• Bug
  • Status: Closed
  • 1 Critical
  • Resolution: Fixed
  • kkannaiy
  • Reporter: ssubbiah
  • October 02, 2008
  • 0
  • Watchers: 0
  • February 12, 2013
  • October 02, 2008

Description

The server crashed with the following exception. Seems like we are creating a lot of threads. From the stack it looks like it is from JMX. Unfortunately the server logs dont have thread dump to see how many such threads are created.

2008-09-19 15:09:43,339 [Job_Executor32] ERROR com.tc.server.TCServerMain - Thread:Thread[Job_Executor32,5,Job_Executor] got an uncaught exception. calling CallbackOnExitHandlers. java.lang.OutOfMemoryError: unable to create new native thread at java.lang.Thread.start0(Native Method) at java.lang.Thread.start(Thread.java:574) at com.sun.jmx.remote.opt.util.JobExecutor.handoff(JobExecutor.java:149) at com.sun.jmx.remote.opt.util.ThreadService.handoff(ThreadService.java:63) at com.sun.jmx.remote.generic.ServerSynchroMessageConnectionImpl.setCallback(ServerSynchroMessageConnectionImpl.java:106) at javax.management.remote.generic.ServerIntermediary.start(ServerIntermediary.java:964) at javax.management.remote.generic.GenericConnectorServer$ClientCreation.run(GenericConnectorServer.java:491) at com.sun.jmx.remote.opt.util.ThreadService$ThreadServiceJob.run(ThreadService.java:208) at com.sun.jmx.remote.opt.util.JobExecutor.run(JobExecutor.java:59)

The L1s seem to have a 100s of the following thread. Dont know if these are causing the server to create the above threads.

“Statistics Retriever Timer” Id=192 WAITING on java.util.TaskQueue@125cbec at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:485) at java.util.TimerThread.mainLoop(Timer.java:483)

Comments