Skip to Content
avatar image
Former Member

deadlock leads to restart of XI java server

hi,

We are currently seeing 1 deadlock found messages in our XI 7 SP15 system, which leads to the restart of the java server in XI, has anyone seen this before .

"Signal Dispatcher" daemon prio=10 tid=0x00000001017e73a0 nid=0x1b waiting on condition [0x0000000000000000..0x0000000000000000]

"Finalizer" daemon prio=8 tid=0x00000001017e36e0 nid=0x19 waiting for monitor entry [0xfffffffe8f3fe000..0xfffffffe8f3ff8b0]

at com.ibm.mq.MQQueueManager.cleanup(MQQueueManager.java:3132)

- waiting to lock <0xfffffffebc649c90> (a com.ibm.mq.MQSPIQueueManager)

at com.ibm.mq.MQQueueManager.disconnect(MQQueueManager.java:2244)

- locked <0xfffffffebc649fe8> (a com.ibm.mq.MQQueueManager)

at com.ibm.mq.MQSESSIONClient.errorCloseComms(MQSESSIONClient.java:2885)

at com.ibm.mq.MQSESSIONClient.MQCLOSE(MQSESSIONClient.java:1068)

at com.ibm.mq.MQManagedObject.close(MQManagedObject.java:396)

- locked <0xfffffffebc649bc8> (a com.ibm.mq.MQSPIQueue)

at com.ibm.mq.MQQueue.close(MQQueue.java:1728)

- locked <0xfffffffebc649bc8> (a com.ibm.mq.MQSPIQueue)

at com.ibm.mq.jms.MQTemporaryQueue.finalize(MQTemporaryQueue.java:101)

at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method)

at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:83)

at java.lang.ref.Finalizer.access$100(Finalizer.java:14)

at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:160)

Mon Jul 13 15:45:30 2009

Found one Java-level deadlock:

=============================

"SAPEngine_Application_Thread[impl:3]_53":

waiting to lock monitor 0x00000001023a2888 (object 0xfffffffebc649bc8, a com.ibm.mq.MQSPIQueue),

which is held by "Finalizer"

"Finalizer":

waiting to lock monitor 0x0000000103798d18 (object 0xfffffffebc649c90, a com.ibm.mq.MQSPIQueueManager),

which is held by "SAPEngine_Application_Thread[impl:3]_53"

Java stack information for the threads listed above:

===================================================

"SAPEngine_Application_Thread[impl:3]_53":

at com.ibm.mq.MQQueue.close(MQQueue.java:1726)

- waiting to lock <0xfffffffebc649bc8> (a com.ibm.mq.MQSPIQueue)

at com.ibm.mq.MQQueueManager.cleanup(MQQueueManager.java:3154)

at com.ibm.mq.MQQueueManager.disconnect(MQQueueManager.java:2244)

- locked <0xfffffffebc649c90> (a com.ibm.mq.MQSPIQueueManager)

at com.ibm.mq.jms.MQConnection.close(MQConnection.java:1212)

at com.ibm.mq.jms.MQQueueConnection.close(MQQueueConnection.java:263)

at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.closeResources(ConnectorImpl.java:585)

at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.doDisconnect(ConnectorImpl.java:332)

at com.sap.aii.adapter.jms.core.connector.BreakDetector.onException(BreakDetector.java:144)

at com.sap.aii.adapter.jms.core.connector.BreakDetector$ConnectionTestPollTask.invoke(BreakDetector.java:219)

at com.sap.aii.af.service.scheduler.JobBroker$Worker.run(JobBroker.java:476)

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:102)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)

"Finalizer":

at com.ibm.mq.MQQueueManager.cleanup(MQQueueManager.java:3132)

- waiting to lock <0xfffffffebc649c90> (a com.ibm.mq.MQSPIQueueManager)

at com.ibm.mq.MQQueueManager.disconnect(MQQueueManager.java:2244)

- locked <0xfffffffebc649fe8> (a com.ibm.mq.MQQueueManager)

at com.ibm.mq.MQSESSIONClient.errorCloseComms(MQSESSIONClient.java:2885)

at com.ibm.mq.MQSESSIONClient.MQCLOSE(MQSESSIONClient.java:1068)

at com.ibm.mq.MQManagedObject.close(MQManagedObject.java:396)

- locked <0xfffffffebc649bc8> (a com.ibm.mq.MQSPIQueue)

at com.ibm.mq.MQQueue.close(MQQueue.java:1728)

- locked <0xfffffffebc649bc8> (a com.ibm.mq.MQSPIQueue)

at com.ibm.mq.jms.MQTemporaryQueue.finalize(MQTemporaryQueue.java:101)

at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method)

at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:83)

at java.lang.ref.Finalizer.access$100(Finalizer.java:14)

at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:160)

Found 1 deadlock.

[Thr 23] Mon Jul 13 15:49:14 2009

[Thr 23] JLaunchIExitJava: exit hook is called (rc = 666)

[Thr 23] **********************************************************************

[Thr 23] SigISetIgnoreAction : SIG_IGN for signal 18

[Thr 23] JLaunchCloseProgram: good bye (exitcode = 666)

Thank you

Jonu Joy

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • avatar image
    Former Member
    Jul 14, 2009 at 06:12 AM

    Hi jonu,

    one time i have faced this situation while giving support to production environment

    then we have to resatrt webdispatcher, jave engine this solved our problem

    thanks

    -- sandeep

    Add comment
    10|10000 characters needed characters exceeded