The error says "unable to create a new native thread." Do you know how many threads you had in this process when it died? The client stats could show the you the number of threads at least. You might also have an hs_err_pid file that might list the threads.
-Dan On Thu, Feb 9, 2017 at 9:23 AM, Barry Oglesby <[email protected]> wrote: > Dharam, > > This stack means that the CacheClientUpdater (which is processing the > messages on the client) has caught an exception, is crashing and kicking > off a thread to recover its connection to the server. A high number of > events alone wouldn't cause this unless the client's queue on the server is > full and remove-unresponsive-client=true in the server. Is that the case? > It would be interesting to see the client and server logs as well as the > server stats to see if we can determine why this is happening. The client > log may contain the exception that is causing the CacheClientUpdater to > crash. > > Thanks, > Barry Oglesby > > > On Thu, Feb 9, 2017 at 2:42 AM, Thacker, Dharam < > [email protected]> wrote: > >> Hi Team, >> >> >> >> I am facing below error while working with continuous query listener. We >> are receiving high number of events matching to various continuous query >> listeners which result into below exception. Though task every thread s >> doing is really very small (Not at all time consuming). >> >> >> >> Any guideline on below one? Is it like thread after finishing work not >> going to pool? >> >> >> >> <gfe:cq-listener-container id=*"cqListenerContainer"* cache= >> *"event-cache"*> >> >> <gfe:listener ref=*"eventListener"* query=*"SELECT * FROM >> /Event WHERE entityType=’A’ and entitySubType IN SET (‘A1’,’A2') and >> status='PENDING'"*/> >> >> </gfe:cq-listener-container> >> >> >> >> [http-nio-8088-exec-14] ERROR o.a.c.c.C.[.[.[.[dispatcherServlet] >> Servlet.service() for servlet [dispatcherServlet] in context with path [] >> threw exception [Handler dispatch failed; nested exception is >> java.lang.OutOfMemoryError: unable to create new native thread] with root >> cause >> >> java.lang.OutOfMemoryError: unable to create new native thread >> >> at java.lang.Thread.start0(Native Method) >> >> at java.lang.Thread.start(Thread.java:714) >> >> at java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPool >> Executor.java:950) >> >> at java.util.concurrent.ThreadPoolExecutor.ensurePrestart(Threa >> dPoolExecutor.java:1587) >> >> at java.util.concurrent.ScheduledThreadPoolExecutor.delayedExec >> ute(ScheduledThreadPoolExecutor.java:334) >> >> at java.util.concurrent.ScheduledThreadPoolExecutor.schedule(Sc >> heduledThreadPoolExecutor.java:533) >> >> at org.apache.geode.cache.client.internal.QueueManagerImpl.sche >> duleRedundancySatisfierIfNeeded(QueueManagerImpl.java:1041) >> >> at org.apache.geode.cache.client.internal.QueueManagerImpl.chec >> kEndpoint(QueueManagerImpl.java:430) >> >> at org.apache.geode.internal.cache.tier.sockets.CacheClientUpda >> ter.processMessages(CacheClientUpdater.java:1811) >> >> at org.apache.geode.internal.cache.tier.sockets.CacheClientUpda >> ter.run(CacheClientUpdater.java:463) >> >> >> >> Thanks & Regards, >> >> Dharam >> >> This email is confidential and subject to important disclaimers and >> conditions including on offers for the purchase or sale of securities, >> accuracy and completeness of information, viruses, confidentiality, legal >> privilege, and legal entity disclaimers, available at >> http://www.jpmorgan.com/pages/disclosures/email >> > >
