PK82994: DEADLOCK DETECTED WHEN A SEND OPERATION IS PERFORMED AGAINST A DESTINATION THAT IS BEING DELETED BY ANOTHER THREAD

Fixes are available

APAR status

Closed as program error.

Error description

The deadlock is most likely to occur when using temporary
destinations, and is between threads with stacks similar to
the following:
Thread "WebContainer : 4" which is closing a connection, and
deleting the temporary destination associated with it:
com/ibm/ws/sib/processor/impl/ProducerSessionImpl.
_closeProducerDestinationDeleted(ProducerSessionImpl.java:703
com/ibm/ws/sib/processor/impl/AbstractInputHandler.
closeProducersDestinationDeleted(AbstractInputHandler.java:511
com/ibm/ws/sib/processor/impl/AbstractDestinationHandler.
closeProducers(AbstractDestinationHandler.java:252
com/ibm/ws/sib/processor/impl/DestinationManager.
deleteDestinationLocalization(DestinationManager.java:2844
com/ibm/ws/sib/processor/impl/DestinationManager.
deleteTemporaryDestination(DestinationManager.java:1966
com/ibm/ws/sib/processor/impl/ConnectionImpl.
deleteTemporaryDestination(ConnectionImpl.java:3620
com/ibm/ws/sib/api/jms/impl/JmsSessionImpl.
deleteTemporaryDestination(JmsSessionImpl.java:3081
com/ibm/ws/sib/api/jms/impl/JmsTemporaryQueueImpl.
delete(JmsTemporaryQueueImpl.java:103
com/ibm/ws/sib/api/jms/impl/JmsConnectionImpl.
close(JmsConnectionImpl.java:742
.......
Thread "SIBThreadPool : 34" which is in the middle of a send
operation against the destination that is being deleted by
"WebContainer : 4":
java/lang/Object.wait(Native Method)
java/lang/Object.wait(Object.java:231(Compiled Code))
com/ibm/ws/sib/processor/utils/LockManager.lock
(LockManager.java:91
com/ibm/ws/sib/processor/impl/PtoPInputHandler.
handleMessage(PtoPInputHandler.java:520
com/ibm/ws/sib/processor/impl/ProducerSessionImpl.
send(ProducerSessionImpl.java:545
com/ibm/ws/sib/api/jms/impl/JmsMsgProducerImpl.
sendMessage(JmsMsgProducerImpl.java:1651
com/ibm/ws/sib/api/jms/impl/JmsMsgProducerImpl.
send(JmsMsgProducerImpl.java:1103

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  Users of the default messaging provider     *
*                  for IBM WebSphere Application Server        *
*                  Version 6.0, Version 6.1 or Version 7.0     *
****************************************************************
* PROBLEM DESCRIPTION: When a thread is deleting a             *
*                      destination while another thread is     *
*                      attempting to send to that              *
*                      destination, a deadlock might occur     *
*                      within the messaging engine.            *
*                                                              *
*                      The messaging engine then becomes       *
*                      unable to process any messaging work,   *
*                      and application threads become          *
*                      blocked.                                *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
If this deadlock is encountered, a javacore shows threads
within the following two methods:
com.ibm.ws.sib.processor.utils.LockManager.lock()
com.ibm.ws.sib.processor.impl.ProducerSessionImpl.
               _closeProducerDestinationDeleted()

The problem is most likely to occur for applications that use
JMS temporary destinations, as in these systems destinations
are created and deleted regularly.

However, it is possible for the problem to be encountered on a
system where temporary destinations are not used. In this
case, a destination must have been deleted administratively
(via the administrative console, or an admin/deployment
script) while the system was actively sending messages to that
destination.

The deadlock is caused by incorrect synchronization within
the messaging engine. The thread deleting the destination
attempts to close the producers attached to that destination
while holding locks that those producers may attempt to gain
while sending a message.

Problem conclusion

The fix for this APAR updates the synchronization of the code
so that threads deleting a destinations do not hold locks that
may be required by producers or consumers, while attempting to
close those producers or consumers.

The fix for this APAR is currently targeted for inclusion in
fix pack 6.0.2.37, 6.1.0.27 and 7.0.0.5.  Please refer to the
Recommended Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PK82994
Reported component name
PLAT MSG COM
Reported component ID
620600101
Reported release
200
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-03-20
Closed date
2009-04-20
Last modified date
2009-04-20

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name
PLAT MSG COM
Fixed component ID
620600101

Applicable component levels

R200 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021

Tips

PK82994: DEADLOCK DETECTED WHEN A SEND OPERATION IS PERFORMED AGAINST A DESTINATION THAT IS BEING DELETED BY ANOTHER THREAD

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R200 PSY

Document Information

Share your feedback

Need support?