Thread Waiting on Condition

From the following thread dump, my thread is waiting on some condition due to the deserialization process. How do I find out what that condition is?
"EventSet Archiving" prio=1 tid=0x081cfb28 nid=0x31ab waiting on condition [619a4000..619a5854]
        at sun.reflect.GeneratedSerializationConstructorAccessor2926.newInstance(Unknown Source)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
        at java.io.ObjectStreamClass.newInstance(ObjectStreamClass.java:788)
        at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1631)
        at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)
        at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1845)
        at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1769)
        at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1646)
        at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)
        at java.io.ObjectInputStream.readObject(ObjectInputStream.java:324)
        at java.util.HashMap.readObject(HashMap.java:1006)
        at sun.reflect.GeneratedMethodAccessor404.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:324)
        at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:838)
        at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1746)
        at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1646)
        at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)
        at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1845)
        at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1769)
        at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1646)
        at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)
        at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1845)
        at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1769)
        at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1646)
        at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)
        at java.io.ObjectInputStream.readObject(ObjectInputStream.java:324)
        at com.dartcontainer.mdc.picaps.dbaccess.EventTable$1.get(EventTable.java:49)
        at com.dartcontainer.mdc.picaps.dbaccess.EventTable$1.get(EventTable.java:44)
        at com.dartcontainer.mdc.picaps.dbaccess.Cache.get(Cache.java:110)
        at com.dartcontainer.mdc.picaps.dbaccess.EventTable.resultToObject(EventTable.java:43)
        at com.dartcontainer.mdc.picaps.dbaccess.EventTable.resultToObject(EventTable.java:24)
        at com.dartcontainer.mdc.picaps.dbaccess.AbstractTable.resultToObject(AbstractTable.java:239)
        at com.dartcontainer.mdc.picaps.dbaccess.EventTable.resultToObject(EventTable.java:24)
        at com.dartcontainer.mdc.picaps.dbaccess.AbstractTable.resultToList(AbstractTable.java:88)
        at com.dartcontainer.mdc.picaps.dbaccess.EventTable.getEvents(EventTable.java:194)
        at com.dartcontainer.mdc.picaps.dbaccess.EventSetPersister.archiveEventsBetween(EventSetPersister.java:149)
        - locked <0x464d73b0> (a com.dartcontainer.mdc.picaps.dbaccess.EventSetPersister)
        at com.dartcontainer.mdc.picaps.dbaccess.EventSetPersister.archiveEvents(EventSetPersister.java:113)
        at com.dartcontainer.mdc.picaps.dbaccess.EventSetPersister.run(EventSetPersister.java:81)
        at java.util.TimerThread.mainLoop(Timer.java:432)
        at java.util.TimerThread.run(Timer.java:382)

The answer you probably don't want to hear, is buy yourself a good profiler.
(e.g. www.jprofiler.com)
Or at least download it and test it during the trial. I'll at least get you through this.
You can profile threads to see what monitor they are waiting on, who has it currently, etc.
Something I like to do is create seperate (inner) classes for each monitor instance I use.
e.g. class IoLock1 extends Object{} IoLock1 lock1 = new IoLock1();This makes things more clear in the profiler which shows the class of the monitor in question.

Similar Messages

Threads stuck in "waiting on condition"

Hi,
Our application is a muti-threaded application which is polling the SNMP network elements. We have used the third-party adventnet API for polling mechanism.
We find that after the application runs for about one day, some of the threads are in 'WAIT' state waiting for a condition for a very long time. The wait is seen in AdventNet's API - SnmpSession.checkSyncResponse.
The pstack output is pasted below:
----------------- lwp# 96 / thread# 96 --------------------
ff2cab38 lwp_cond_wait (baee90, baee78, f0cfee88, 0)
ff2b1d98 lwpcond_timedwait (baee90, baee78, f0cfef20, 39f4e40, 6d3c, e7d390) + 1c
fecf61ec __1cNObjectMonitorEwait6MxipnGThread__v_ (6c00, baee78, f0cfef20, ff17f8d0, baee90, ff1a0930) + 778
fecf59c4 __1cSObjectSynchronizerEwait6FnGHandle_xpnGThread__v_ (baebe0, 0, 64, ff17f914, f0cff00c, 497c) + d8
fecf55d8 JVM_MonitorWait (0, bae784, 0, 64, baebe0, ff1869e4) + 2f0
f9135170 * *java/lang/Object.wait(J)V
f953bba4 * *com/adventnet/snmp/snmp2/SnmpSession.checkSyncResponse(I)I+46 (line 2585)
f953ca60 * *com/adventnet/snmp/snmp2/SnmpSession.getResponse(IJZ)Lcom/adventnet/snmp/snmp2/SnmpPDU;+8 (line 2483)
f9005874 * com/adventnet/snmp/snmp2/SnmpSession.syncSend(Lcom/adventnet/snmp/snmp2/SnmpPDU;)Lcom/adventnet/snmp/snmp2/SnmpPDU;+105 (line 2415)
f9005874 * com/adventnet/snmp/snmp2/SnmpEngineEntry.discoverSnmpEngineID(Lcom/adventnet/snmp/snmp2/SnmpSession;II)[B+326 (line 673)
f9005874 * com/adventnet/snmp/snmp2/SnmpEngineEntry.discoverSnmpEngineID(Lcom/adventnet/snmp/snmp2/SnmpSession;)[B+4 (line 566)
f9005874 * com/adventnet/snmp/snmp2/usm/USMUtils.doDiscovery(Lcom/adventnet/snmp/snmp2/SnmpSession;Lcom/adventnet/snmp/snmp2/ProtocolOptions;)Lcom/adventnet/snmp/snmp2/SnmpEngineEntry;+199 (line 1629)
f9005874 * com/adventnet/snmp/snmp2/usm/USMUtils.init_v3_parameters(Ljava/lang/String;[BILjava/lang/String;Ljava/lang/String;Lcom/adventnet/snmp/snmp2/ProtocolOptions;Lcom/adventnet/snmp/snmp2/SnmpSession;Z)V+159 (line 1270)
f98351fc * *com/adventnet/snmp/beans/SnmpServer.create_v3_tables()I+578 (line 2542)
f90058b8 * com/alcatel/omc/nodebim/snmpmediation/polling/PollingTimerTask.addSnmpEntries()V+95 (line 1015)
f9884000 * *com/alcatel/omc/nodebim/snmpmediation/polling/PollingTimerTask.poll()V+865 (line 438)
f9005764 * com/alcatel/omc/nodebim/snmpmediation/polling/PollerManagerServant.poll(Lcom/alcatel/omc/nodebim/snmpmediation/polling/SnmpMe     diationPoller;)V+4 (line 264)
f9005764 * com/alcatel/omc/nodebim/snmpmediation/polling/PollRequest.call()V+8 (line 55)
f99f249c * *com/alcatel/omc/fwk/activeobjects/Scheduler.run()V+250 (line 192)
f910e938 * com/alcatel/omc/fwk/activeobjects/Scheduler.run()V+105 (line 186)
f9000218 * StubRoutines (1)
fecdd540 __1cJJavaCallsLcall_helper6FpnJJavaValue_pnMmethodHandle_pnRJavaCallArguments_pnGThread__v_ (1, baebe0, f0cffb98, f0cffab8, f0cffb9c, 0) + 5b8
fecf4f80 __1cJJavaCallsMcall_virtual6FpnJJavaValue_nGHandle_nLKlassHandle_nMsymbolHandle_5pnGThread__v_ (596c, baebe0, bae770, bae77c, baeb5c, b110de18) + 18c
fecf4ddc __1cMthread_entry6FpnKJavaThread_pnGThread__v_ (b110de18, baebe0, ff195cac, d5812ad8, bae770, ff195798) + 12c
fecf4c60 __1cKJavaThreadDrun6M_v_ (baebe0, 4c00, ff18435c, 0, 6400, ff16c000) + 2d0
ff03cc90 __1cG_start6Fpv_0_ (baebe0, ff186a1c, ff17f8dc, 0, 3418, ff16c000) + 200
ff2c6d4c _lwp_start (0, 0, 0, 0, 0, 0)
----------------- lwp# 97 / thread# 97 --------------------
ff2cab38 lwp_cond_wait (bafab0, bafa98, 0, 0)
fecf5fcc __1cNObjectMonitorEwait6MxipnGThread__v_ (bafab0, bafa98, ff1953c8, 0, ff1a0930, bafa70) + 558
fecf59c4 __1cSObjectSynchronizerEwait6FnGHandle_xpnGThread__v_ (baeeb0, 0, 0, ff17f914, f0bff6fc, 497c) + d8
fecf55d8 JVM_MonitorWait (0, baf494, 0, 0, baeeb0, ff1869e4) + 2f0
f9135170 * *java/lang/Object.wait(J)V
f9812aa4 * *java/lang/Object.wait()V+2 (line 474)
f9812aa4 * *EDU/oswego/cs/dl/util/concurrent/BoundedBuffer.take()Ljava/lang/Object;+73 (line 164)
f99f20b4 * *com/alcatel/omc/fwk/activeobjects/Scheduler.run()V+189 (line 189)
f910e938 * com/alcatel/omc/fwk/activeobjects/Scheduler.run()V+105 (line 186)
f9000218 * StubRoutines (1)
fecdd540 __1cJJavaCallsLcall_helper6FpnJJavaValue_pnMmethodHandle_pnRJavaCallArguments_pnGThread__v_ (1, baeeb0, f0bffb18, f0bffa38, f0bffb1c, 0) + 5b8
fecf4f80 __1cJJavaCallsMcall_virtual6FpnJJavaValue_nGHandle_nLKlassHandle_nMsymbolHandle_5pnGThread__v_ (596c, baeeb0, baf480, baf48c, baf86c, b110f6f0) + 18c
fecf4ddc __1cMthread_entry6FpnKJavaThread_pnGThread__v_ (b110f6f0, baeeb0, ff195cac, d5812ad8, baf480, ff195798) + 12c
fecf4c60 __1cKJavaThreadDrun6M_v_ (baeeb0, 4c00, ff18435c, 0, 6400, ff16c000) + 2d0
ff03cc90 __1cG_start6Fpv_0_ (baeeb0, ff186a1c, ff17f8dc, 0, 3418, ff16c000) + 200
ff2c6d4c _lwp_start (0, 0, 0, 0, 0, 0)
On checking the AdventNet API, it seems that there is an explicit wait called only for 100milliseconds. Could someone let me know why these threads are blocked in waiting state for a very long time?
Regards,
Padma

Anand_Sharma wrote:
Hi,
Our application is a muti-threaded application which is polling the SNMP servers. We have used the third-party adventnet API for polling mechanism.
Can it be an application issue?
This looks like an application issue in Adventent
===========================
----------------- lwp# 6921 / thread# 6921 --------------------
ffffffff7eed3890 lwp_mutex_timedlock (10011be40, 0)
ffffffff7e25b4d8 __1cHMonitorEwait6Mil_i_ (ffffffff7e78e210, 120660740, ffffffff7e78ff94, ffffffff7e7943fc, 9800, 9ba8) + 328
ffffffff7e2b5f08 __1cIVMThreadHexecute6FpnMVM_Operation__v_ (ffffffff7e78e2f0, 0, a000, a2e8, c558, 3fea88) + 228
ffffffff7e30929c __1cODeoptimizationNuncommon_trap6FpnKJavaThread_i_pn0ALUnrollBlock__ (124da4140, fffffffffffffffc, fffffffffffffffc, ff000000, 100, 0) + 874The frames below are java frames. It has called monitor.wait().
ffffffff7606c940 ???????? (fffffffffffffffc, 3, fffffffe365cc558, 11, 6, 817fe2)
ffffffff764eea1c ???????? (fffffffe365c17e8, ffffffff724c0848, fffffffe365c1ee8, fffffffe365c1820, ffffffff71c63190, fffffffa910feec0)
"Device Poller Thread" prio=5 tid=0x0000000124da4140 nid=0x1b09 waiting on condition [0xfffffffa910fe000..0xfffffffa910ff8b0]
     at com.adventnet.snmp.snmp2.ASNTypes.encodeLength(ASNTypes.java:105)This java method above has called monitor.wait(). If you have access to the adventnet take a look at it and see why it is waiting here.
jstack on 1.6 can detect deadlock. Run jstack on this and find out if there is any deadlock. I suspect the thread supposed to notify these waiting threads might have got stuck.

Waiting on condition at java.lang.FloatingDecimal.floatValue(FloatingDecima

Hello Experts,
I am facing an issue while executing "floatValue" method of BIgdecimal Object.when the control comes to above method ,webdynpro application is going into infinite loop.this is working fine on all systems(development ,test..) except production.
i found one difference in test and production system.Both are running on different java versions.is it causing this issue?
test server is running on 1.4.2.17 and production is running on 1.4.2.12 version.
here is the thread dump that i got in server:
"SAPEngine_Application_Threadimpl:3_13ID#(J2EE25213200)D1139794350DB10384483039162372751End.6f1b61d0d00d11dcc73e001560dee930" tid=0x60000000037db8d0 nid=0x45 prio=10 waiting on condition
at java.lang.FloatingDecimal.floatValue(FloatingDecimal.java:1710)
at java.lang.Float.valueOf(Float.java:205)
at java.math.BigDecimal.floatValue(BigDecimal.java:1012)
at com.sap.xltest.components.mpfxl.xl.XLCust.mCreateXL(XLCust.java:787)
at com.sap.xltest.components.mpfxl.xl.wdp.InternalXLCust.mCreateXL(InternalXLCust.java:306)
at com.sap.xltest.components.mpfxl.MPFXLCompInterface.imCreateXL(MPFXLCompInterface.java:115)
at com.sap.xltest.components.mpfxl.wdp.InternalMPFXLCompInterface.imCreateXL(InternalMPFXLCompInterface.java:296)
at com.sap.xltest.components.mpfxl.wdp.InternalMPFXLCompInterface$External.imCreateXL(InternalMPFXLCompInterface.java:348)
at com.pg.pftp.selectionscreen.views.selectionscreen.SelectionScreenView.onActionasimplDownload(SelectionScreenView.java:1395)
at com.pg.pftp.selectionscreen.views.selectionscreen.wdp.InternalSelectionScreenView.wdInvokeEventHandler(InternalSelectionScreenView.java:731)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:101)
at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:304)
at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:659)
- locked<0x9fffffff3df65718> (a com.sap.tc.webdynpro.clientserver.cal.ClientApplication)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251)
- locked<0x9fffffff3e15de50> (a com.sap.tc.webdynpro.clientimpl.html.client.HtmlClient)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
any help will be greatly appriciated.
Thanks in advance
with regards,
Balaram Naidu

Hi,
yes the version of java is the problem.you have to maintain samejava version in all server.if your version is same then there is no problem.

Waiting on condition at java.lang.FloatingDecimal.floatValue(FloatingDec.)

Hello Experts,
i am facing an issue while executing floatValue method of BIgdecimal Object.when the control comes to that statement ,application is going into infinite loop.this is working fine on all systems(development ,test..) except production.
i found one difference in test and production system.both are running in different java versions.is it causing this issue?
test server is running on 1.4.2.17 and production is running on 1.4.2.12 version.
here is the thread dump that i got in server:
D1139794350DB10384483039162372751End.6f1b61d0d00d11dcc73e001560dee930" tid=0x60000000037db8d0 nid=0x45 prio=10 waiting on condition
at java.lang.FloatingDecimal.floatValue(FloatingDecimal.java:1710)
at java.lang.Float.valueOf(Float.java:205)
at java.math.BigDecimal.floatValue(BigDecimal.java:1012)
at com.test.method(XLCust.java:787)
at com.
at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:101)
at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:304)
at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:659)
- locked<0x9fffffff3df65718> (a com.sap.tc.webdynpro.clientserver.cal.ClientApplication)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251)
- locked<0x9fffffff3e15de50> (a com.sap.tc.webdynpro.clientimpl.html.client.HtmlClient)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
any help will be greatly appriciated.
thanks in advance
with regards
Naidu

Hi,
yes the version of java is the problem.you have to maintain samejava version in all server.if your version is same then there is no problem.

Waiting on condition at at java.lang.FloatingDecimal.floatValue(FloatingDec

Hello Experts,
i am facing an issue while executing floatValue method of BIgdecimal Object.when the control comes to that statement ,application is going into infinite loop.this is working fine on all systems(development ,test..) except production.
i found one difference in test and production system.both are running in different java versions.is it causing this issue?
test server is running on 1.4.2.17 and production is running on 1.4.2.12 version.
here is the thread dump that i got in server:
D1139794350DB10384483039162372751End.6f1b61d0d00d11dcc73e001560dee930" tid=0x60000000037db8d0 nid=0x45 prio=10 waiting on condition
     at java.lang.FloatingDecimal.floatValue(FloatingDecimal.java:1710)
     at java.lang.Float.valueOf(Float.java:205)
     at java.math.BigDecimal.floatValue(BigDecimal.java:1012)
     at com.test.method(XLCust.java:787)
     at com.
     at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
     at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:101)
     at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:304)
     at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:659)
     - locked<0x9fffffff3df65718> (a com.sap.tc.webdynpro.clientserver.cal.ClientApplication)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
     at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251)
     - locked<0x9fffffff3e15de50> (a com.sap.tc.webdynpro.clientimpl.html.client.HtmlClient)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
any help will be greatly appriciated.
thanks in advance
with regards
Naidu

Hi,
yes the version of java is the problem.you have to maintain samejava version in all server.if your version is same then there is no problem.

How to make the main() thread wait?

I would like to know how to make the main() thread wait for another thread?If I use wait() method in main() method it says "non-static method wait() cannot be referenced from a static context",since main()
is static.

Here is an example how you may wait for a Thread in the main -
but be careful, this is no real OO:
public class WaitMain {
// this is the thread class - you may also create
// a runnable - I use a inner class to
// keep my example simple
     public static class ThreadWait extends Thread{
          public void doSomething(){
               synchronized(syncObject){
                    System.out.println("Do Something");
                    syncObject.notify();
          public void run(){
               // sleep 10 seconds - this is
               // a placeholder to do something in the thread
               try{
                    sleep(10000);
                    doSomething();
                    sleep(10000);
               catch(InterruptedException exc){
// this is the object we wait for -
// it is just a synchronizer, nothing else
     private static Object syncObject = new Object();
     public static void main(String[] args) {
          System.out.println("This will start a thread and wait for \"doSomething\"");
          ThreadWait t= new ThreadWait();
          t.start();
          synchronized(syncObject){
               try{
// this will wait for the notify
                    syncObject.wait();
                    System.out.println("The doSomething is now over!");
               catch(InterruptedException exc){
          // do your stuff

How to change 'Wait for condition' period?

Hi all
I am using a workflow with a 'wait for condition' step in it. It takes so long to wait, how I reduce the waiting time?
I think it should be a periodly job in background to check the condition, but I don't know which one it is~

Hi
The job name is SWWCOND change the job schedule timing for every 1 min. Your wait step will be executed after every 1 min. User name is WF-BATCH.
Regards
vijay

Jstack shows a thread waiting for monitor entry but it's already acquired

I have a heavy load website powered by tomcat-6.0.14 and jdk1.6.0_02-b05(amd64) on a 2 dual-core amd Opteron. When tomcat started, and I directed the http request(~200/s) abruptly to tomcat, it looks choked for over one minute, and if I took off the http requests, tomcat can recover in a few minutes.
Then I use jstack during the choke time to find what's the cause, where I found a strange situation. Almost all threads are blocking on getting a log4j lock(I think it's normal,since log4j use a coarse lock), but one thread which already got the lock are also blocked. Below is the stack trace.
"http-172.23.24.29-8011-exec-175" daemon prio=10 tid=0x00002aad37843400 nid=0x542d waiting for monitor entry [0x0000000052e55000..0x0000000052e55da0]
java.lang.Thread.State: BLOCKED (on object monitor)
at org.apache.log4j.Category.callAppenders(Category.java:201)
- locked <0x00002aaab39d5670> (a org.apache.log4j.spi.RootLogger)
at org.apache.log4j.Category.forcedLog(Category.java:388)
at org.apache.log4j.Category.log(Category.java:853)
at org.apache.commons.logging.impl.Log4JLogger.info(Log4JLogger.java:133)
at com.xxx.xxxx.TimingLogFilter.doFilter(TimingLogFilter.java:39)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:263)
at org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:887)
at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:696)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2009)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)
And all the other threads waiting for the log4j lock.
"http-172.23.24.29-8011-exec-176" daemon prio=10 tid=0x00002aad37773800 nid=0x542e waiting for monitor entry [0x0000000052f56000..0x0000000052f56b20]
java.lang.Thread.State: BLOCKED (on object monitor)
at org.apache.log4j.Category.callAppenders(Category.java:201)
- waiting to lock <0x00002aaab39d5670> (a org.apache.log4j.spi.RootLogger)
at org.apache.log4j.Category.forcedLog(Category.java:388)
at org.apache.log4j.Category.log(Category.java:853)
at org.apache.commons.logging.impl.Log4JLogger.info(Log4JLogger.java:133)
at com.xxx.xxxxx.TimingLogFilter.doFilter(TimingLogFilter.java:39)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:263)
at org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:887)
at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:696)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2009)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)
I'm really wondering why jstack shows the first thread is BLOCKED but no blocker.
And also, it's not a deadlock, since I made jstack log after sever seconds, and found this time another thread has the same problem.
"http-172.23.24.29-8011-exec-170" daemon prio=10 tid=0x00002aad3784d800 nid=0x5428 waiting for monitor entry [0x0000000052950000..0x0000000052950c20]
java.lang.Thread.State: BLOCKED (on object monitor)
at org.apache.log4j.Category.callAppenders(Category.java:201)
- locked <0x00002aaab39d5670> (a org.apache.log4j.spi.RootLogger)
at org.apache.log4j.Category.forcedLog(Category.java:388)
at org.apache.log4j.Category.log(Category.java:853)
at org.apache.commons.logging.impl.Log4JLogger.info(Log4JLogger.java:133)
at com.xxx.xxxx.TimingLogFilter.doFilter(TimingLogFilter.java:35)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:263)
at org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:887)
at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:696)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2009)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)
What's the cause? Is jstack accurate? Or, the problem is caused by hotspot compling since tomcat is just started? Or it's just because log4j's coarse lock? ( but after the starup, tomcat can handle the same traffic without any problem, and jstack shows no log4j block at all.)
Thanks in advance.
Jimcgnu

"http-172.23.24.29-8011-exec-175" daemon prio=10 tid=0x00002aad37843400 nid=0x542d waiting for monitor entry [0x0000000052e55000..0x0000000052e55da0]
java.lang.Thread.State: BLOCKED (on object monitor)
at org.apache.log4j.Category.callAppenders(Category.java:201)
- locked <0x00002aaab39d5670> (a org.apache.log4j.spi.RootLogger)
It seems like a Dead Lock.
The thread must have entered into a synchronized block/method1() and acquired a lock.
- locked <0x00002aaab39d5670> (a org.apache.log4j.spi.RootLogger)
While having lock the thread might be trying to acquire a lock to another synchronized block/method2()
waiting for monitor entry
java.lang.Thread.State: BLOCKED (on object monitor)
and someother thread might have already acquired a lock to that block/method2().
Can we check for Dead Lock??

Workflow - WAIT for Condition not working

Dear All,
This is regarding the WAIT step of workflow. It was used as WAIT for Condition. The condition is to check the application server's time (system field) with some local variable of time. Till this step meets the condition specified, the workflow will wait for some x hours. If this condition is satisfied, the workflow is expected to continue with the next steps.
During the execution of the workflow, the wait step history shows that it is created successfully. But in ready status only. In the graphical log it shows <i>No Agent </i> along with this wait step.
There is no field wherein I could assign this agent. Also the job SWWDHEX is working fine.
Kindly help in sorting out this issue.
Thanks & Regards

Hi Rob,
Thanks for your response. I tried using the Deadline monitoring in Activity step. I tried using the Requested Start tab with Expression for this step. The requirement is to hold the processing for some x hours depending on following business requirements -
If there is a ticket for issue with New status then wait for X hours. During this X hours the technician is supposed to acknowledge the ticket. So hold the workflow for X hours and as the X hours are over, check for ticket status. If the ticket status is still new then escalate it to managers saying ticket not acknowledged using Send Mail step.
Hence I had to ask the workflow to wait for some X hours.
The Requested Start tab requires the reference Date/Time + a direct input value (ZZ) for min or hour or day etc fields.
Now here the Time field is either a reference time AT which the activity will start with a delay of the ZZ Min/Hours/Day that we give in the next field OR this Time is exact value of time for which the workflow should hold.
e.g.
1.
Date 27-Dec-06
Time 00:10:00
+ 1 min
then here it is either 11 min, the workflow should hold for processing or
it is on 27th Dec 2006, 12 past 10'O clock time and when this time reaches, the workflow should wait for 1 min and then proceed.
As none of the above logics were working. So I couldn't exactly make out what this Time field actually requires. I thought it was time when reaches the workflow should hold for some ZZ min.
Again, the time value what I can give to this workflow is of application server time. But in the log of the workflow shows that work item refers to presentation server time everywhere. Hence it is difficult to compare also.
So finally I took a wait step wherein both the variables of the time were given to starting event of workflow.
Kindly help me in sorting out this issue.
Thanks & Regards

Threads waiting the same event

hi all,
i have two thread waiting an event
and another who notify them
//the class event
public final class Event {
* variable used to store the notification if it takes place
* before being expected
private boolean status = false;
public final synchronized void waitForNotification() {
while (status == false ) {
try {
wait();
catch (InterruptedException e) {
status = false ;
// notify all waits on this event
public final synchronized void wakeUp() {
status = true;
notifyAll();
// the class TestThread implements a thread that have an event waiting for a notification
public class TestThread extends Thread{
private Event event;
public TestThread( Event e){
event=e;
public void run(){
for (int i = 1; i < 4; i += 1) {
try {
Thread.sleep(2);
} catch (InterruptedException e) {
// TODO Auto-generated catch block
e.printStackTrace();
e.waitForNotification();
// the class TestThread2 implements a thread that have an event waiting for a notification
public class TestThread2 extends Thread{
private Event event;
public TestThread( Event e){
event=e;
public void run(){
for (int i = 1; i < 4; i += 1) {
e.wakeUp();
//the class main
public class test {
* @param args
public static void main(String[] args) {
// TODO Auto-generated method stub
Event e = new event();
TestThread th1 = new TestThreadConsumer(e);
TestThread th2 = new TestThread(e);
TestThread2 th= new TestThread2(e);
th1.start();
th2.start();
th3.start();
1st case
the problem is that the notification could not be seen to the tow threads
because if the tow are waiting the notification
and the other thread send notification
one of the tow see the notificztion and wake up and set the flag status to false so the other one could not ever wake up
2d case
the notification of the second thread could be done in the second itiration or in the other ones
please could u answer and help me
thank you

nabila.abdessaied wrote:
i just wanna to have tow thread waiting a notification from another
and when another send the notification
they could go out from waiting and do their jobHi.
Below is an example of how you could do this. It is taken from http://www.javaconcurrencyinpractice.com/listings.html (5.11 Using CountDownLatch for starting and stopping threads in timing tests) .
The idea is simple:
(1) main thread starts nThreads, but all of them, once started, are "suspended" in startGate.await();
(2) when all threads are started, main thread calls startGate.countDown(); and all those waiting threads "are off" at once.
I'm not sure that you need 'endGate' though (but I thought that it is not that good to cut somebody's else example...)
* TestHarness
* <p/>
* Using CountDownLatch for starting and stopping threads in timing tests
* @author Brian Goetz and Tim Peierls
public class TestHarness {
    public long timeTasks(int nThreads, final Runnable task)
            throws InterruptedException {
        final CountDownLatch startGate = new CountDownLatch(1);
        final CountDownLatch endGate = new CountDownLatch(nThreads);
        for (int i = 0; i < nThreads; i++) {
            Thread t = new Thread() {
                public void run() {
                    try {
                        startGate.await();
                        try {
                            task.run();
                        } finally {
                            endGate.countDown();
                    } catch (InterruptedException ignored) {
            t.start();
        long start = System.nanoTime();
        startGate.countDown();
        endGate.await();
        long end = System.nanoTime();
        return end - start;
}Seems this is what you were looking for (if I understood you right).

Threads waiting the same event :searching for a specific notificationfor

hi all,
i have two thread waiting an event
and another who notify them
//the class event
public final class Event {
* variable used to store the notification if it takes place
* before being expected
private boolean status = false;
public final synchronized void waitForNotification() {
while (status == false ) {
try {
wait();
catch (InterruptedException e) {
status = false ;
// notify all waits on this event
public final synchronized void wakeUp() {
status = true;
notifyAll();
// the class TestThread implements a thread that have an event waiting for a notification
public class TestThread extends Thread{
private Event event;
public TestThread( Event e){
event=e;
public void run(){
for (int i = 1; i < 4; i += 1) {
try {
Thread.sleep(2);
} catch (InterruptedException e) {
// TODO Auto-generated catch block
e.printStackTrace();
e.waitForNotification();
// the class TestThread2 implements a thread that have an event waiting for a notification
public class TestThread2 extends Thread{
private Event event;
public TestThread( Event e){
event=e;
public void run(){
for (int i = 1; i < 4; i += 1) {
e.wakeUp();
//the class main
public class test {
* @param args
public static void main(String[] args) {
// TODO Auto-generated method stub
Event e = new event();
TestThread th1 = new TestThreadConsumer(e);
TestThread th2 = new TestThread(e);
TestThread2 th= new TestThread2(e);
th1.start();
th2.start();
th3.start();
1st case
the problem is that the notification could not be seen to the tow threads
because if the tow are waiting the notification
and the other thread send notification
one of the tow see the notificztion and wake up and set the flag status to false so the other one could not ever wake up
2d case
the notification of the second thread could be done in the second itiration or in the other ones
please could u answer and help me
thank you

I'm locking this thread since it's a duplicate.
The discussion will continue in: [http://forums.sun.com/thread.jspa?threadID=5377151&tstart=0]
Kaj

How to count the Threads, waiting on object's lock?

Hello!
I have a vector of the objects. Some threads are waiting on this objects using method wait() to be notified on this object's monitor.
I will remove an object from the vector in order to save a memory, if there is no threads waiting on it, but how I undestand it?

You could keep count on how many threads are waiting
on a particular object and then you'd know it's OK to
remove the object if this count is zero. Then, of
course, you'd have to modify your code to increment
one such count each time a thread is about to call
wait() and decrement it after the wait() call. (If you
do that then remember to synchronize the counter
modification code properly.)Simple way to do this...
In the object that is being waited on, if you can extend it...
int nWaiting = 0;
public synchronized void doWait() {
   nWaiting++;
   wait();
   nWaiting--;
public sychronized int waitingCount() {
   return nWaiting;
}Note that this count may still be off if some code uses wait() instead of doWait(). If you have control over the objects that are supposed to be waiting on a given monitor, then waitingCount() will give you an indication of if any are currently waiting.
Hope this helps,
-Troy

Memory usage in Thread wait()

Hi all,
I have a question.
What is the memory usage (in terms of RAM, not of virtual memory) if 1000 Threads wait for a long time on a common object suppose for more than one day?
Will be they moved to disk memory and then in RAM when a notify() occurs or what else? Thanks! Bye

Ok,
I understood your answers but I see the scenario is not clear.
Suppose a program has to launch and high number of threads. Some of these threads will wait on a monitor for a large period of time (in terms of days...) and others will have no wait at all.
Eg. Think as half the threads that run on the JVM blocks on a monitor and the other half not. Suppose we create 1000 thread every 5 second.
So we have this kind of evolution in one minute
12 * 1000 Threads are created
12 * 500 Thread will wait on a monitor (for a very long time)
What the JVM does with this thread? Will the JVM move this threads for RAM to disk or will it keep them in RAM?
In other words, what is the runtime memory usage of the JVM when a thread waits for a very long time? Will it temporary free the memory of the thread, saving it in the disk or will it keep it in RAM?
I hope I've been clear now! Bye

Many threads in waitforrequest condition and server in unknown condition

Java version : J2RE 5.0 IBM J9 2.3 AIX ppc-32 build j9vmap3223-20080315
Maximum Java heap size : 2048m
Initial Java heap size : 1024m
Free Java heap size: 656,758,528 bytes
Allocated Java heap size: 1,477,712,384 bytes
I have application deployed on above environment.Using Springs2.0,Struts 2.0 and JPA
Many threads in waiting condition no deadlock condition.**Application has stopped respondinThread dump looks like
2XMFULLTHDDUMP Full thread dump J9 VM (J2RE 5.0 IBM J9 2.3 AIX ppc-32 build 20080314_17962_bHdSMr, native threads):
"main" (TID:0x3295C400, sys_thread_t:0x300107E8, state:CW, native ID:0x001980FB) prio=5
at java/lang/Object.wait(Native Method)
at java/lang/Object.wait(Object.java:199)
at weblogic/t3/srvr/T3Srvr.waitForDeath(T3Srvr.java:730)
at weblogic/t3/srvr/T3Srvr.run(T3Srvr.java:380)
at weblogic/Server.main(Server.java:67)
"JIT Compilation Thread" (TID:0x3295C800, sys_thread_t:0x30010D20, state:CW, native ID:0x001E70A5) prio=11
"Signal Dispatcher" (TID:0x3295CC00, sys_thread_t:0x30011258, state:R, native ID:0x00260001) prio=5
at com/ibm/misc/SignalDispatcher.waitForSignal(Native Method)
at com/ibm/misc/SignalDispatcher.run(SignalDispatcher.java:84)
"Concurrent Mark Helper" (TID:0x33CF8C00, sys_thread_t:0x33C19EE4, state:CW, native ID:0x0014203D) prio=5
"Gc Slave Thread" (TID:0x33CF9000, sys_thread_t:0x33C1A180, state:CW, native ID:0x0025B0B7) prio=5
"Timer-0" (TID:0x33CF9400, sys_thread_t:0x33C1A41C, state:CW, native ID:0x000C50E7) prio=5
at java/lang/Object.wait(Native Method)
at java/lang/Object.wait(Object.java:199(Compiled Code))
at java/util/TimerThread.mainLoop(Timer.java:498)
at java/util/TimerThread.run(Timer.java:477)
"Timer-1" (TID:0x34C3EF00, sys_thread_t:0x33C1A6B8, state:CW, native ID:0x001400E3) prio=5
at java/lang/Object.wait(Native Method)
at java/lang/Object.wait(Object.java:231(Compiled Code))
at java/util/TimerThread.mainLoop(Timer.java:524)
at java/util/TimerThread.run(Timer.java:477)
"[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'" (TID:0x34C3F300, sys_thread_t:0x33C1A954, state:CW, native ID:0x0019E0EF) prio=5
at java/lang/Object.wait(Native Method)
at java/lang/Object.wait(Object.java:199(Compiled Code))
at weblogic/work/ExecuteThread.waitForRequest(ExecuteThread.java:163(Compiled Code))
at weblogic/work/ExecuteThread.run(ExecuteThread.java:186)
"OperatingSystemMXBean notification dispatcher" (TID:0x34C3F700, sys_thread_t:0x35525028, state:CW, native ID:0x0018F031) prio=6
at com/ibm/lang/management/OperatingSystemNotificationThread.processNotificationLoop(Native Method)
at com/ibm/lang/management/OperatingSystemNotificationThread.run(OperatingSystemNotificationThread.java:39)
"MemoryPoolMXBean notification dispatcher" (TID:0x3557B200, sys_thread_t:0x355252C4, state:CW, native ID:0x001D508D) prio=6
at com/ibm/lang/management/MemoryNotificationThread.processNotificationLoop(Native Method)
at com/ibm/lang/management/MemoryNotificationThread.run(MemoryNotificationThread.java:55)
"weblogic.time.TimeEventGenerator" (TID:0x3557B600, sys_thread_t:0x35525560, state:CW, native ID:0x0021C055) prio=9
at java/lang/Object.wait(Native Method)
at java/lang/Object.wait(Object.java:231(Compiled Code))
at weblogic/time/common/internal/TimeTable.snooze(TimeTable.java:286)
at weblogic/time/common/internal/TimeEventGenerator.run(TimeEventGenerator.java:117)
at java/lang/Thread.run(Thread.java:810)
"weblogic.timers.TimerThread" (TID:0x3557BA00, sys_thread_t:0x355257FC, state:CW, native ID:0x001CF047) prio=9
at java/lang/Object.wait(Native Method)
at java/lang/Object.wait(Object.java:231(Compiled Code))
at weblogic/timers/internal/TimerThread$Thread.run(TimerThread.java:260)
"[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'" (TID:0x355A8300, sys_thread_t:0x35525A98, state:CW, native ID:0x002230A5) prio=5
at java/lang/Object.wait(Native Method)
at java/lang/Object.wait(Object.java:199(Compiled Code))
at weblogic/work/ExecuteThread.waitForRequest(ExecuteThread.java:163(Compiled Code))
at weblogic/work/ExecuteThread.run(ExecuteThread.java:186)
"Finalizer thread" (TID:0x355A8700, sys_thread_t:0x35525D34, state:CW, native ID:0x00258071) prio=5
"weblogic.store.WLS_DIAGNOSTICS" (TID:0x355A8B00, sys_thread_t:0x33CB7518, state:P, native ID:0x002390F1) prio=10
at sun/misc/Unsafe.park(Native Method)
at java/util/concurrent/locks/LockSupport.park(LockSupport.java:169(Compiled Code))
at java/util/concurrent/locks/AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1787(Compiled Code))
at java/util/concurrent/LinkedBlockingQueue.take(LinkedBlockingQueue.java:379(Compiled Code))
at weblogic/utils/concurrent/JDK15ConcurrentBlockingQueue.take(JDK15ConcurrentBlockingQueue.java:89(Compiled Code))
at weblogic/store/internal/PersistentStoreImpl.getOutstandingWork(PersistentStoreImpl.java:570(Compiled Code))
at weblogic/store/internal/PersistentStoreImpl.run(PersistentStoreImpl.java:618)
at java/lang/Thread.run(Thread.java:810)
"ExecuteThread: '0' for queue: 'weblogic.socket.Muxer'" (TID:0x33E56300, sys_thread_t:0x33CB77B4, state:B, native ID:0x0013A019) prio=5
at weblogic/socket/PosixSocketMuxer.processSockets(PosixSocketMuxer.java:93)
at weblogic/socket/SocketReaderRequest.run(SocketReaderRequest.java:29)
at weblogic/socket/SocketReaderRequest.execute(SocketReaderRequest.java:42)
at weblogic/kernel/ExecuteThread.execute(ExecuteThread.java:145)
at weblogic/kernel/ExecuteThread.run(ExecuteThread.java:117)
"ExecuteThread: '1' for queue: 'weblogic.socket.Muxer'" (TID:0x33E56700, sys_thread_t:0x33CB7A50, state:B, native ID:0x001B4053) prio=5
at weblogic/socket/PosixSocketMuxer.processSockets(PosixSocketMuxer.java:93)
at weblogic/socket/SocketReaderRequest.run(SocketReaderRequest.java:29)
at weblogic/socket/SocketReaderRequest.execute(SocketReaderRequest.java:42)
at weblogic/kernel/ExecuteThread.execute(ExecuteThread.java:145)
at weblogic/kernel/ExecuteThread.run(ExecuteThread.java:117)
"ExecuteThread: '2' for queue: 'weblogic.socket.Muxer'" (TID:0x33E56B00, sys_thread_t:0x33CB7CEC, state:R, native ID:0x00208083) prio=5
at weblogic/socket/PosixSocketMuxer.poll(Native Method)
at weblogic/socket/PosixSocketMuxer.processSockets(PosixSocketMuxer.java:102)
at weblogic/socket/SocketReaderRequest.run(SocketReaderRequest.java:29)
at weblogic/socket/SocketReaderRequest.execute(SocketReaderRequest.java:42)
at weblogic/kernel/ExecuteThread.execute(ExecuteThread.java:145)
at weblogic/kernel/ExecuteThread.run(ExecuteThread.java:117)
"VDE Transaction Processor Thread" (TID:0x33F9F300, sys_thread_t:0x33CB7F88, state:CW, native ID:0x002050A9) prio=2
at java/lang/Object.wait(Native Method)
at java/lang/Object.wait(Object.java:199)
at com/octetstring/vde/backend/standard/TransactionProcessor.waitChange(TransactionProcessor.java:367)
at com/octetstring/vde/backend/standard/TransactionProcessor.run(TransactionProcessor.java:212)
"LDAPConnThread-0 ldap://10.18.49.5:7001" (TID:0x33F9F700, sys_thread_t:0x33CB8224, state:R, native ID:0x001D10AB) prio=5
at java/net/SocketInputStream.socketRead0(Native Method)
at java/net/SocketInputStream.read(SocketInputStream.java:155)
at java/io/BufferedInputStream.fill(BufferedInputStream.java:229)
at java/io/BufferedInputStream.read(BufferedInputStream.java:246(Compiled Code))
at netscape/ldap/ber/stream/BERElement.getElement(BERElement.java:101)
at netscape/ldap/LDAPConnThread.run(LDAPConnThread.java:538)
at java/lang/Thread.run(Thread.java:810)
"DoSManager" (TID:0x33F9FB00, sys_thread_t:0x33F4F638, state:CW, native ID:0x000940C3) prio=6
at java/lang/Thread.sleep(Native Method)
at java/lang/Thread.sleep(Thread.java:938(Compiled Code))
at com/octetstring/vde/DoSManager.run(DoSManager.java:433)
"LDAPConnThread-1 ldap://10.18.49.5:7001" (TID:0x3414EE00, sys_thread_t:0x33F4F8D4, state:R, native ID:0x00189037) prio=5
at java/net/SocketInputStream.socketRead0(Native Method)
at java/net/SocketInputStream.read(SocketInputStream.java:155)
at java/io/BufferedInputStream.fill(BufferedInputStream.java:229)
at java/io/BufferedInputStream.read(BufferedInputStream.java:246(Compiled Code))
at netscape/ldap/ber/stream/BERElement.getElement(BERElement.java:101)
at netscape/ldap/LDAPConnThread.run(LDAPConnThread.java:538)
at java/lang/Thread.run(Thread.java:810)
"weblogic.store._WLS_TPMS_MS1" (TID:0x3414F200, sys_thread_t:0x33F4FB70, state:P, native ID:0x001C70AF) prio=10
at sun/misc/Unsafe.park(Native Method)
at java/util/concurrent/locks/LockSupport.park(LockSupport.java:169(Compiled Code))
at java/util/concurrent/locks/AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1787(Compiled Code))
at java/util/concurrent/LinkedBlockingQueue.take(LinkedBlockingQueue.java:379(Compiled Code))
at weblogic/utils/concurrent/JDK15ConcurrentBlockingQueue.take(JDK15ConcurrentBlockingQueue.java:89)
at weblogic/store/internal/PersistentStoreImpl.getOutstandingWork(PersistentStoreImpl.java:570(Compiled Code))
at weblogic/store/internal/PersistentStoreImpl.run(PersistentStoreImpl.java:618)
at java/lang/Thread.run(Thread.java:810)
"Store com.cvs.tpms.cache.METHOD_CACHE Spool Thread" (TID:0x3414F600, sys_thread_t:0x33F4FE0C, state:CW, native ID:0x002510DD) prio=2
at java/lang/Thread.sleep(Native Method)
at java/lang/Thread.sleep(Thread.java:938(Compiled Code))
at net/sf/ehcache/store/DiskStore.spoolAndExpiryThreadMain(DiskStore.java:573)
at net/sf/ehcache/store/DiskStore.access$800(DiskStore.java:65)
at net/sf/ehcache/store/DiskStore$SpoolAndExpiryThread.run(DiskStore.java:1057)
"[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'" (TID:0x3B886200, sys_thread_t:0x33F500A8, state:CW, native ID:0x00257023) prio=5
at java/lang/Object.wait(Native Method)
at java/lang/Object.wait(Object.java:199(Compiled Code))
at weblogic/work/ExecuteThread.waitForRequest(ExecuteThread.java:163(Compiled Code))
at weblogic/work/ExecuteThread.run(ExecuteThread.java:186)
"weblogic.GCMonitor" (TID:0x3B886600, sys_thread_t:0x33F50344, state:CW, native ID:0x0027309D) prio=5
at java/lang/Object.wait(Native Method)
at java/lang/Object.wait(Object.java:231(Compiled Code))
at java/lang/ref/ReferenceQueue.remove(ReferenceQueue.java:97(Compiled Code))
at weblogic/platform/GCMonitorThread.waitForNotification(GCMonitorThread.java:88)
at weblogic/platform/GCMonitorThread.run(GCMonitorThread.java:64)
"[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'" (TID:0x3B886A00, sys_thread_t:0x3B6DE538, state:CW, native ID:0x0026400B) prio=5
at java/lang/Object.wait(Native Method)
at java/lang/Object.wait(Object.java:199(Compiled Code))
at weblogic/work/ExecuteThread.waitForRequest(ExecuteThread.java:163(Compiled Code))
at weblogic/work/ExecuteThread.run(ExecuteThread.java:186)
"DynamicListenThread[Default]" (TID:0x3ACF6F00, sys_thread_t:0x3B6DE7D4, state:CW, native ID:0x0022E04F) prio=9
at java/net/PlainSocketImpl.socketAccept(Native Method)
at java/net/PlainSocketImpl.accept(PlainSocketImpl.java:455(Compiled Code))
at java/net/ServerSocket.implAccept(ServerSocket.java:462(Compiled Code))
at java/net/ServerSocket.accept(ServerSocket.java:433(Compiled Code))
at weblogic/socket/WeblogicServerSocket.accept(WeblogicServerSocket.java:34(Compiled Code))
at weblogic/server/channels/DynamicListenThread$SocketAccepter.accept(DynamicListenThread.java:519(Compiled Code))
at weblogic/server/channels/DynamicListenThread$SocketAccepter.access$200(DynamicListenThread.java:420(Compiled Code))
at weblogic/server/channels/DynamicListenThread.run(DynamicListenThread.java:166)
at java/lang/Thread.run(Thread.java:810)
"[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'" (TID:0x3ACF7300, sys_thread_t:0x3B6DEA70, state:CW, native ID:0x001AA0EF) prio=5
at java/lang/Object.wait(Native Method)
at java/lang/Object.wait(Object.java:199(Compiled Code))
at weblogic/work/ExecuteThread.waitForRequest(ExecuteThread.java:163(Compiled Code))
at weblogic/work/ExecuteThread.run(ExecuteThread.java:186)
"[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'" (TID:0x3ACF7700, sys_thread_t:0x3B6DED0C, state:CW, native ID:0x0014C03F) prio=5
at java/lang/Object.wait(Native Method)
at java/lang/Object.wait(Object.java:199(Compiled Code))
at weblogic/work/ExecuteThread.waitForRequest(ExecuteThread.java:163(Compiled Code))
at weblogic/work/ExecuteThread.run(ExecuteThread.java:186)
"Thread-17" (TID:0x3BE6F600, sys_thread_t:0x3B6DEFA8, state:CW, native ID:0x000B209D) prio=5
at java/lang/Object.wait(Native Method)
at java/lang/Object.wait(Object.java:231(Compiled Code))
at com/sun/jmx/remote/internal/ServerCommunicatorAdmin$Adminor.run(ServerCommunicatorAdmin.java:163)
at java/lang/Thread.run(Thread.java:810)
"FSCacheRefQueueThread" (TID:0x3BE6FA00, sys_thread_t:0x3B6DF244, state:CW, native ID:0x0019A0A9) prio=1
at java/lang/Object.wait(Native Method)
at java/lang/Object.wait(Object.java:231(Compiled Code))
at java/lang/ref/ReferenceQueue.remove(ReferenceQueue.java:97(Compiled Code))
at java/lang/ref/ReferenceQueue.remove(ReferenceQueue.java:74(Compiled Code))
at workshop/util/filesystem/FSCache$FSCacheRefQueueThread.run(FSCache.java:65)
"[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'" (TID:0x3BE6FE00, sys_thread_t:0x3F621978, state:R, native ID:0x0019F0BF) prio=5
at java/net/PlainSocketImpl.socketClose0(Native Method)
at java/net/PlainSocketImpl.socketPreClose(PlainSocketImpl.java:744(Compiled Code))
at java/net/PlainSocketImpl.close(PlainSocketImpl.java:568(Compiled Code))
at java/net/SocksSocketImpl.close(SocksSocketImpl.java:1049(Compiled Code))
at java/net/Socket.close(Socket.java:1341(Compiled Code))
at weblogic/socket/SocketMuxer.closeSocket(SocketMuxer.java:430(Compiled Code))
at weblogic/socket/SocketMuxer.cancelIo(SocketMuxer.java:754)
at weblogic/socket/SocketMuxer.deliverExceptionAndCleanup(SocketMuxer.java:744(Compiled Code))
at weblogic/socket/SocketMuxer.deliverEndOfStream(SocketMuxer.java:681)
at weblogic/socket/SocketMuxer.closeSocket(SocketMuxer.java:558)
at weblogic/rjvm/t3/MuxableSocketT3$T3MsgAbbrevJVMConnection.close(MuxableSocketT3.java:510)
at weblogic/rjvm/ConnectionManager.removeConnection(ConnectionManager.java:1183)
at weblogic/rjvm/ConnectionManager.shutdown(ConnectionManager.java:718)
at weblogic/rjvm/ConnectionManagerServer.shutdown(ConnectionManagerServer.java:733)
at weblogic/rjvm/RJVMImpl.peerGone(RJVMImpl.java:1321)
at weblogic/rjvm/RJVMImpl$HeartbeatChecker.timerExpired(RJVMImpl.java:1516(Compiled Code))
at weblogic/timers/internal/TimerImpl.run(TimerImpl.java:265(Compiled Code))
at weblogic/work/ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518(Compiled Code))
at weblogic/work/ExecuteThread.execute(ExecuteThread.java:209(Compiled Code))
at weblogic/work/ExecuteThread.run(ExecuteThread.java:181(Compiled Code))
"[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'" (TID:0x3FF82400, sys_thread_t:0x3F621EB0, state:CW, native ID:0x0019208D) prio=5
at java/lang/Object.wait(Native Method)
at java/lang/Object.wait(Object.java:199(Compiled Code))
at weblogic/work/ExecuteThread.waitForRequest(ExecuteThread.java:163(Compiled Code))
at weblogic/work/ExecuteThread.run(ExecuteThread.java:173(Compiled Code))
"[ACTIVE] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'" (TID:0x3FF82800, sys_thread_t:0x3F621C14, state:CW, native ID:0x0024E0A5) prio=5
at java/lang/Object.wait(Native Method)
at java/lang/Object.wait(Object.java:199(Compiled Code))
at weblogic/work/ExecuteThread.waitForRequest(ExecuteThread.java:163(Compiled Code))
at weblogic/work/ExecuteThread.run(ExecuteThread.java:173(Compiled Code))
"[STANDBY] ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)'" (TID:0x3FF82C00, sys_thread_t:0x3F62214C, state:CW, native ID:0x001950F3) prio=5
at java/lang/Object.wait(Native Method)
at java/lang/Object.wait(Object.java:199(Compiled Code))
at weblogic/work/ExecuteThread.waitForRequest(ExecuteThread.java:163(Compiled Code))
at weblogic/work/ExecuteThread.run(ExecuteThread.java:173(Compiled Code))
"File Reaper" (TID:0x400CEF00, sys_thread_t:0x406E4F48, state:CW, native ID:0x001EC0F5) prio=10
at java/lang/Object.wait(Native Method)
at java/lang/Object.wait(Object.java:231(Compiled Code))
at java/lang/ref/ReferenceQueue.remove(ReferenceQueue.java:97(Compiled Code))
at java/lang/ref/ReferenceQueue.remove(ReferenceQueue.java:74(Compiled Code))
at org/apache/commons/io/FileCleaner$Reaper.run(FileCleaner.java:206)
"[STANDBY] ExecuteThread: '12' for queue: 'weblogic.kernel.Default (self-tuning)'" (TID:0x41008500, sys_thread_t:0x406E5480, state:CW, native ID:0x0026107F) prio=5
at java/lang/Object.wait(Native Method)
at java/lang/Object.wait(Object.java:199(Compiled Code))
at weblogic/work/ExecuteThread.waitForRequest(ExecuteThread.java:163(Compiled Code))
at weblogic/work/ExecuteThread.run(ExecuteThread.java:173(Compiled Code))
"[ACTIVE] ExecuteThread: '26' for queue: 'weblogic.kernel.Default (self-tuning)'" (TID:0x42C39000, sys_thread_t:0x42C0F4EC, state:CW, native ID:0x002120AF) prio=5
at java/lang/Object.wait(Native Method)
at java/lang/Object.wait(Object.java:199(Compiled Code))
at weblogic/work/ExecuteThread.waitForRequest(ExecuteThread.java:163(Compiled Code))
at weblogic/work/ExecuteThread.run(ExecuteThread.java:173(Compiled Code))
"[ACTIVE] ExecuteThread: '27' for queue: 'weblogic.kernel.Default (self-tuning)'" (TID:0x42D70C00, sys_thread_t:0x42C0F788, state:CW, native ID:0x001320CF) prio=5
at java/lang/Object.wait(Native Method)
at java/lang/Object.wait(Object.java:199(Compiled Code))
at weblogic/work/ExecuteThread.waitForRequest(ExecuteThread.java:163(Compiled Code))
at weblogic/work/ExecuteThread.run(ExecuteThread.java:173(Compiled Code))
"[ACTIVE] ExecuteThread: '28' for queue: 'weblogic.kernel.Default (self-tuning)'" (TID:0x42D71000, sys_thread_t:0x42C0FA24, state:CW, native ID:0x002140D9) prio=5
at java/lang/Object.wait(Native Method)
at java/lang/Object.wait(Object.java:199(Compiled Code))
at weblogic/work/ExecuteThread.waitForRequest(ExecuteThread.java:163(Compiled Code))
at weblogic/work/ExecuteThread.run(ExecuteThread.java:173(Compiled Code))
"[ACTIVE] ExecuteThread: '29' for queue: 'weblogic.kernel.Default (self-tuning)'" (TID:0x42D71400, sys_thread_t:0x42E4A648, state:CW, native ID:0x002320EB) prio=5
at java/lang/Object.wait(Native Method)
at java/lang/Object.wait(Object.java:199(Compiled Code))
at weblogic/work/ExecuteThread.waitForRequest(ExecuteThread.java:163(Compiled Code))
at weblogic/work/ExecuteThread.run(ExecuteThread.java:173(Compiled Code))
"[ACTIVE] ExecuteThread: '30' for queue: 'weblogic.kernel.Default (self-tuning)'" (TID:0x42E54700, sys_thread_t:0x42E4A8E4, state:CW, native ID:0x001B80B7) prio=5
at java/lang/Object.wait(Native Method)
at java/lang/Object.wait(Object.java:199(Compiled Code))
at weblogic/work/ExecuteThread.waitForRequest(ExecuteThread.java:163(Compiled Code))
at weblogic/work/ExecuteThread.run(ExecuteThread.java:173(Compiled Code))
"[ACTIVE] ExecuteThread: '31' for queue: 'weblogic.kernel.Default (self-tuning)'" (TID:0x42E54B00, sys_thread_t:0x42E4AB80, state:CW, native ID:0x001E6031) prio=5
at java/lang/Object.wait(Native Method)
at java/lang/Object.wait(Object.java:199(Compiled Code))
at weblogic/work/ExecuteThread.waitForRequest(ExecuteThread.java:163(Compiled Code))
at weblogic/work/ExecuteThread.run(ExecuteThread.java:173(Compiled Code))
"[ACTIVE] ExecuteThread: '32' for queue: 'weblogic.kernel.Default (self-tuning)'" (TID:0x42E54F00, sys_thread_t:0x42E4AE1C, state:CW, native ID:0x001550EF) prio=5
at java/lang/Object.wait(Native Method)
at java/lang/Object.wait(Object.java:199(Compiled Code))
at weblogic/work/ExecuteThread.waitForRequest(ExecuteThread.java:163(Compiled Code))
at weblogic/work/ExecuteThread.run(ExecuteThread.java:173(Compiled Code))
"[ACTIVE] ExecuteThread: '33' for queue: 'weblogic.kernel.Default (self-tuning)'" (TID:0x42E75700, sys_thread_t:0x42E4B0B8, state:CW, native ID:0x00268027) prio=5
at java/lang/Object.wait(Native Method)
at java/lang/Object.wait(Object.java:199(Compiled Code))
at weblogic/work/ExecuteThread.waitForRequest(ExecuteThread.java:163(Compiled Code))
at weblogic/work/ExecuteThread.run(ExecuteThread.java:173(Compiled Code))
"[ACTIVE] ExecuteThread: '34' for queue: 'weblogic.kernel.Default (self-tuning)'" (TID:0x42E75B00, sys_thread_t:0x42E4B354, state:CW, native ID:0x000CC093) prio=5
at java/lang/Object.wait(Native Method)
at java/lang/Object.wait(Object.java:199(Compiled Code))
at weblogic/work/ExecuteThread.waitForRequest(ExecuteThread.java:163(Compiled Code))
at weblogic/work/ExecuteThread.run(ExecuteThread.java:173(Compiled Code))
"[ACTIVE] ExecuteThread: '35' for queue: 'weblogic.kernel.Default (self-tuning)'" (TID:0x42E75F00, sys_thread_t:0x42E7D6A8, state:CW, native ID:0x001CE0F9) prio=5
at java/lang/Object.wait(Native Method)
at java/lang/Object.wait(Object.java:199(Compiled Code))
at weblogic/work/ExecuteThread.waitForRequest(ExecuteThread.java:163(Compiled Code))
at weblogic/work/ExecuteThread.run(ExecuteThread.java:173(Compiled Code))
"[ACTIVE] ExecuteThread: '36' for queue: 'weblogic.kernel.Default (self-tuning)'" (TID:0x42E86800, sys_thread_t:0x42E7D944, state:CW, native ID:0x0014D0FB) prio=5
at java/lang/Object.wait(Native Method)
at java/lang/Object.wait(Object.java:199(Compiled Code))
at weblogic/work/ExecuteThread.waitForRequest(ExecuteThread.java:163(Compiled Code))
at weblogic/work/ExecuteThread.run(ExecuteThread.java:173(Compiled Code))
"[ACTIVE] ExecuteThread: '37' for queue: 'weblogic.kernel.Default (self-tuning)'" (TID:0x42E86C00, sys_thread_t:0x42E7DBE0, state:CW, native ID:0x001A909F) prio=5
at java/lang/Object.wait(Native Method)
at java/lang/Object.wait(Object.java:199(Compiled Code))
at weblogic/work/ExecuteThread.waitForRequest(ExecuteThread.java:163(Compiled Code))
at weblogic/work/ExecuteThread.run(ExecuteThread.java:173(Compiled Code))
"[STANDBY] ExecuteThread: '38' for queue: 'weblogic.kernel.Default (self-tuning)'" (TID:0x42E87000, sys_thread_t:0x42E7DE7C, state:CW, native ID:0x0012608B) prio=5
at java/lang/Object.wait(Native Method)
at java/lang/Object.wait(Object.java:199(Compiled Code))
at weblogic/work/ExecuteThread.waitForRequest(ExecuteThread.java:163(Compiled Code))
at weblogic/work/ExecuteThread.run(ExecuteThread.java:173(Compiled Code))
"[STANDBY] ExecuteThread: '45' for queue: 'weblogic.kernel.Default (self-tuning)'" (TID:0x43701E00, sys_thread_t:0x4346B748, state:CW, native ID:0x001D90ED) prio=5
at java/lang/Object.wait(Native Method)
at java/lang/Object.wait(Object.java:199(Compiled Code))
at weblogic/work/ExecuteThread.waitForRequest(ExecuteThread.java:163(Compiled Code))
at weblogic/work/ExecuteThread.run(ExecuteThread.java:173(Compiled Code))
"[STANDBY] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'" (TID:0x43702200, sys_thread_t:0x4346B9E4, state:CW, native ID:0x0018D031) prio=5
at java/lang/Object.wait(Native Method)
at java/lang/Object.wait(Object.java:199(Compiled Code))
at weblogic/work/ExecuteThread.waitForRequest(ExecuteThread.java:163(Compiled Code))
at weblogic/work/ExecuteThread.run(ExecuteThread.java:173(Compiled Code))
"[STANDBY] ExecuteThread: '47' for queue: 'weblogic.kernel.Default (self-tuning)'" (TID:0x43702600, sys_thread_t:0x4374F2A8, state:CW, native ID:0x001E80D1) prio=5
at java/lang/Object.wait(Native Method)
at java/lang/Object.wait(Object.java:199(Compiled Code))
at weblogic/work/ExecuteThread.waitForRequest(ExecuteThread.java:163(Compiled Code))
at weblogic/work/ExecuteThread.run(ExecuteThread.java:173(Compiled Code))
"[ACTIVE] ExecuteThread: '48' for queue: 'weblogic.kernel.Default (self-tuning)'" (TID:0x437E0D00, sys_thread_t:0x4374F544, state:CW, native ID:0x0013C075) prio=5
at java/lang/Object.wait(Native Method)
at java/lang/Object.wait(Object.java:199(Compiled Code))
at weblogic/work/ExecuteThread.waitForRequest(ExecuteThread.java:163(Compiled Code))
at weblogic/work/ExecuteThread.run(ExecuteThread.java:173(Compiled Code))
"[ACTIVE] ExecuteThread: '49' for queue: 'weblogic.kernel.Default (self-tuning)'" (TID:0x437E1100, sys_thread_t:0x4374F7E0, state:R, native ID:0x000FF091) prio=5
at java/net/PlainSocketImpl.socketClose0(Native Method)
at java/net/PlainSocketImpl.socketPreClose(PlainSocketImpl.java:744(Compiled Code))
at java/net/PlainSocketImpl.close(PlainSocketImpl.java:568(Compiled Code))
at java/net/SocksSocketImpl.close(SocksSocketImpl.java:1049(Compiled Code))
at java/net/Socket.close(Socket.java:1341(Compiled Code))
at weblogic/socket/WeblogicSocket.close(WeblogicSocket.java:80(Compiled Code))
at weblogic/socket/SocketMuxer.closeSocket(SocketMuxer.java:420(Compiled Code))
at weblogic/socket/SocketMuxer.cancelIo(SocketMuxer.java:754)
at weblogic/socket/SocketMuxer$TimerListenerImpl.timerExpired(SocketMuxer.java:957(Compiled Code))
at weblogic/timers/internal/TimerImpl.run(TimerImpl.java:265(Compiled Code))
at weblogic/work/ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518(Compiled Code))
at weblogic/work/ExecuteThread.execute(ExecuteThread.java:209(Compiled Code))
at weblogic/work/ExecuteThread.run(ExecuteThread.java:181(Compiled Code))
Any help will be highly appreciated.

My jvm parameters....Weblogic is 9.2
-Xjcl:jclscar_23
-Dcom.ibm.oti.vm.bootstrap.library.path=/usr/java5/jre/bin
-Dsun.boot.library.path=/usr/java5/jre/bin
-Djava.library.path=/usr/java5/jre/bin:/usr/java5/jre/bin:/usr/java5/jre/bin/classic:/usr/java5/jre/bin:/usr/local/bea/weblogic921/patch_weblogic921/profiles/default/native:/usr/local/CA/Siteminder/webagent/bin:/usr/local/bea/weblogic921/weblogic92/server/native/aix/ppc:/usr/java5/jre/bin/j9vm:/usr/lib
-Djava.home=/usr/java5/jre
-Djava.ext.dirs=/usr/java5/jre/lib/ext
-Duser.dir=/usr/local/bea/weblogic921/user_projects/domains/tpms
j2sej9=70912 0xF0AF7C68
vfprintf 0x300017C4
-Xms1024m
-Xmx2048m
-Xmn312m
-Xgcpolicy:gencon
-da
-Dplatform.home=/usr/local/bea/weblogic921/weblogic92
-Dwls.home=/usr/local/bea/weblogic921/weblogic92/server
-Dwli.home=/usr/local/bea/weblogic921/weblogic92/integration
-Dweblogic.management.discover=false
-Dweblogic.management.server=http://ibmtpmsua1:7001
-Dwlw.iterativeDev=false
-Dwlw.testConsole=false
-Dwlw.logErrorsToConsole=
-Dweblogic.ext.dirs=/usr/local/bea/weblogic921/patch_weblogic921/profiles/default/sysext_manifest_classpath
-Dweblogic.Name=TPMS_MS1
-Djava.security.policy=/usr/local/bea/weblogic921/weblogic92/server/lib/weblogic.policy
-Dinvokedviajava
-Djava.class.path=/usr/local/bea/weblogic921/user_projects/domains/tpms/patches/CR287255_810sp6_v2.jar/usr/local/bea:/usr/local/bea/weblogic921/patch_weblogic921/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/usr/java5/lib/tools.jar:/usr/local/bea/weblogic921/weblogic92/server/lib/weblogic_sp.jar:/usr/local/bea/weblogic921/weblogic92/server/lib/weblogic.jar:/usr/local/bea/weblogic921/weblogic92/server/lib/webservices.jar::/usr/local/bea/weblogic921/weblogic92/common/eval/pointbase/lib/pbclient51.jar:/usr/local/bea/weblogic921/weblogic92/server/lib/xqrl.jar::
vfprintf
portlibrary 0xF0AF74A8
-Xdump
-Xjcl:jclscar_23
-Dcom.ibm.oti.vm.bootstrap.library.path=/usr/java5/jre/bin
-Dsun.boot.library.path=/usr/java5/jre/bin
-Djava.library.path=/usr/java5/jre/bin:/usr/java5/jre/bin:/usr/java5/jre/bin/classic:/usr/java5/jre/bin:/usr/local/bea/weblogic921/patch_weblogic921/profiles/default/native:/usr/local/CA/Siteminder/webagent/bin:/usr/local/bea/weblogic921/weblogic92/server/native/aix/ppc:/usr/java5/jre/bin/j9vm:/usr/lib
-Djava.home=/usr/java5/jre
-Djava.ext.dirs=/usr/java5/jre/lib/ext
-Duser.dir=/usr/local/bea/weblogic921/user_projects/domains/tpms
j2sej9=70912 0xF0AF7C68
vfprintf 0x300017C4
-Xms1024m
-Xmx2048m
-Xmn312m
-Xgcpolicy:gencon
-da
-Dplatform.home=/usr/local/bea/weblogic921/weblogic92
-Dwls.home=/usr/local/bea/weblogic921/weblogic92/server
-Dwli.home=/usr/local/bea/weblogic921/weblogic92/integration
-Dweblogic.management.discover=false
-Dweblogic.management.server=http://ibmtpmsua1:7001
-Dwlw.iterativeDev=false
-Dwlw.testConsole=false
-Dwlw.logErrorsToConsole=
-Dweblogic.ext.dirs=/usr/local/bea/weblogic921/patch_weblogic921/profiles/default/sysext_manifest_classpath
-Dweblogic.Name=TPMS_MS1
-Djava.security.policy=/usr/local/bea/weblogic921/weblogic92/server/lib/weblogic.policy
-Dinvokedviajava
-Djava.class.path=/usr/local/bea/weblogic921/user_projects/domains/tpms/patches/CR287255_810sp6_v2.jar/usr/local/bea:/usr/local/bea/weblogic921/patch_weblogic921/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/usr/java5/lib/tools.jar:/usr/local/bea/weblogic921/weblogic92/server/lib/weblogic_sp.jar:/usr/local/bea/weblogic921/weblogic92/server/lib/weblogic.jar:/usr/local/bea/weblogic921/weblogic92/server/lib/webservices.jar::/usr/local/bea/weblogic921/weblogic92/common/eval/pointbase/lib/pbclient51.jar:/usr/local/bea/weblogic921/weblogic92/server/lib/xqrl.jar::
vfprintf
portlibrary 0xF0AF74A8
-Xdump

Photoshop Elements Organizer 11 crashes due to deadlock in the thread wait chain when creating thumbnails for *.mts (AVCHD) files

Hi,
the Elements Organizer 11 creates a deadlock in the wait chain when generating thumbnails for more than a handful of MTS (AVCHD) files.
After importing AVCHD files from my Canon video camera, the organizer using default settings always crashes. I was able to narrow down the problem to be caused by thumbnail generating.
After deactivating the automatic generation of thumbnails, the organizer does not crash any more upon launching .
Of course, working without thumbnails is not very practical. The next resort is manual trigger of thumbnail generation by selecting "update thumbnail".
If I manually trigger updating of thumbnails for files one by one, then it works for quite many files before crashing again.
Selecting thumbnail update for multiple files at once has a much higher likelihood to crash.
This does not seem to be related to particular file contents: a file that leads to crashing once may be flawlessly get a thumbnail created at the next attempt.
The Windows event report looks as follows (German language Windows):
Name der fehlerhaften Anwendung: PhotoshopElementsOrganizer.exe, Version: 11.0.0.0, Zeitstempel: 0x505e9f67
Name des fehlerhaften Moduls: msvcrt.dll, Version: 7.0.9600.16384, Zeitstempel: 0x52158ff5
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00009919
ID des fehlerhaften Prozesses: 0x13c8
Startzeit der fehlerhaften Anwendung: 0x01cfb676145d0c54
Pfad der fehlerhaften Anwendung: C:\Program Files (x86)\Adobe\Elements 11 Organizer\PhotoshopElementsOrganizer.exe
Pfad des fehlerhaften Moduls: C:\WINDOWS\SYSTEM32\msvcrt.dll
Berichtskennung: b8817e29-2269-11e4-bf2d-10bf487f7b28
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:
Occasionally, a different module is listed as erroneous instead of msvcrt.dll.
My questions:
- has anyone experienced the same problem?
- is this a known issue with Organizer 11?
- is the issue solved with Organizer 12?
I have Premiere Elements 11, Photoshop Elements 11 installed and not experienced any other issues with these applications.
Playback of said AVCHD (*.mts) files works flawlessly, i.e. I do not have any codec or performance issue on my PC.
Deactivation of anti-virus software has no significant effect. I have excluded video directories from scanning anyways.
Have deactivated face recognition, visual search and smart tagging in the organizer.
Have also disabled hyperthreading in the BIOS.
Using Windows XP compatibility settings for PSE somewhat improved the stability, but did not completely eliminate crashes.
Additionally, it signnificantly slows down thumbnail generation and a progress indication window becomes visible during thumbnail generation, which is barely noticable in native Win 8.1 mode.
Officially, Elements 11 is compatible with Windows 8.1.
There is a knowledgebase article related to Elements 6, which recommends to disable multi-threading and to enforce execution of Organizer on more than one core.
This reduces the problem a little bit, but thumbnailing more than a handful of files still leads to crashing.
By means of the task manager, I analyzed the wait chain of the process PhotoshopElementsOrganizer.exe:
Every time the fault occurs, it is caused by a deadlock in the wait chain.
For example:
PhotoshopElementsOrganizer.exe (PID:6440) Thread: 6540
-- PhotoshopElementsOrganizer.exe (PID:6440) Thread: 5932
---- PhotoshopElementsOrganizer.exe (PID:6440) Thread: 6540
PhotoshopElementsOrganizer.exe (PID:6440) Thread: 5932
-- PhotoshopElementsOrganizer.exe (PID:6440) Thread: 6540
---- PhotoshopElementsOrganizer.exe (PID:6440) Thread: 5932
Regards
Oliver
Microsoft Windows 8.1 Pro, 64bit, 6.3.9600 Build 9600
Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz,
16 GB RAM
AMD Radeon HD5450, 1GB
256 GB SSD, Crucial M4-CT256 (Windows, Application, Swap and Temp files), NTFS
1.8 TB HDD, WesternDigital, WD2002FAEX-007BA0, NTFS (media store)

Hi,
I'm experiencing the same problem after importing MTS files.
When you said that you unisntall all other codec, what do you mean?
Codec Inside element software?
I have desable the automatic thumbnail and it still crash.
I'M running the software and trying to import more video files and the program keep crashing during the process of selecting the files in the directory to be imported.
i went in my windows 7 journal and here is the error.
System
Provider
[ Name]
Application Error
EventID
1000
[ Qualifiers]
0
Level
2
Task
100
Keywords
0x80000000000000
TimeCreated
[ SystemTime]
2014-08-31T19:36:04.000000000Z
EventRecordID
244366
Channel
Application
Computer
Ordi-Denis
Security
EventData
PhotoshopElementsOrganizer.exe
11.0.0.0
503fdd1d
MSACM32.dll
6.1.7600.16385
4a5bda4e
c0000005
00004d91
1634
01cfc552c927dce5
C:\Program Files (x86)\Adobe\Elements 11 Organizer\PhotoshopElementsOrganizer.exe
C:\Windows\system32\MSACM32.dll
0b097e53-3146-11e4-a14e-bcaec51a14f7
Please i need help since Adobe is not helping us.

Thread Waiting on Condition

Similar Messages

Maybe you are looking for