PK79362: Runtime problems using the WebSphere MQ messaging provider in WebSphere Application Server.

Fixes are available

APAR status

Closed as program error.

Error description

Errors thrown at runtime when using the WebSphere MQ Resource
Adapter in WebSphere Application Server.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  Users of WebSphere Application Server       *
*                  7.0 using WebSphere MQ as a messaging       *
*                  provider.                                   *
****************************************************************
* PROBLEM DESCRIPTION: Issues may be experienced at runtime    *
*                      when using WebSphere MQ as a messaging  *
*                      provider.                               *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
WebSphere MQ RA related threads may deadlock when the
WebSphere MQ RA is being used in WebSphere Application Server.
Meaning that any processing involving the WebSphere MQ RA
might hang. The automatically generated Javacore will show a
deadlock detected involving 2 or more WebSphere MQ RA threads,
e.g.

1LKDEADLOCK    Deadlock detected !!!
NULL           ---------------------
NULL
2LKDEADLOCKTHR  Thread "WMQJCAResourceAdapter : 8"
(0x0000000001F7D400)
3LKDEADLOCKWTR    is waiting for:
4LKDEADLOCKMON      sys_mon_t:0x0000040013AB7140 infl_mon_t:
0x0000040013AB71B0:
4LKDEADLOCKOBJ
java/lang/String@00000000121E4680/00000000121E468C:
3LKDEADLOCKOWN    which is owned by:
2LKDEADLOCKTHR  Thread "WMQCommonServices : 53"
(0x000000000203B300)
3LKDEADLOCKWTR    which is waiting for:
4LKDEADLOCKMON      sys_mon_t:0x0000040013AB50C0 infl_mon_t:
0x0000040013AB5130:
4LKDEADLOCKOBJ
java/lang/String@00000000121E46C0/00000000121E46CC:
3LKDEADLOCKOWN    which is owned by:
2LKDEADLOCKTHR  Thread "WMQJCAResourceAdapter : 8"
(0x0000000001F7D400)

These threads would have stack traces which looked similar to
the following:

4XESTACKTRACE          at
com/ibm/ejs/jms/JMSConnectionHandle.markManagedConnectionAsStale
(JMSConnectionHandle.java:871)
4XESTACKTRACE          at
com/ibm/ejs/jms/JMSConnectionHandle.<relevant interface method>

or

4XESTACKTRACE          at
com/ibm/ejs/jms/JMSConnectionHandle.invalidate(JMSConnectionHand
le.java:954)
4XESTACKTRACE          at
com/ibm/ejs/jms/JMSConnectionHandle.invalidate(JMSConnectionHand
le.java:956)
4XESTACKTRACE          at
com/ibm/ejs/jms/JMSConnectionHandle.invalidate(JMSConnectionHand
le.java:956)
4XESTACKTRACE          at
com/ibm/ejs/jms/JMSConnectionHandle.invalidate(JMSConnectionHand
le.java:956)
4XESTACKTRACE          at
com/ibm/ejs/jms/JMSConnectionHandle.invalidate(JMSConnectionHand
le.java:956)
4XESTACKTRACE          at
com/ibm/ejs/jms/JMSConnectionHandle.invalidate(JMSConnectionHand
le.java:956)
4XESTACKTRACE          at
com/ibm/ejs/jms/JMSConnectionHandle.invalidate(JMSConnectionHand
le.java:956)
4XESTACKTRACE          at
com/ibm/ejs/jms/JMSConnectionHandle.invalidate(JMSConnectionHand
le.java:956)
4XESTACKTRACE          at
com/ibm/ejs/jms/JMSConnectionHandle.invalidate(JMSConnectionHand
le.java:956)
4XESTACKTRACE          at
com/ibm/ejs/jms/JMSConnectionHandle.invalidate(JMSConnectionHand
le.java:956)
4XESTACKTRACE          at
com/ibm/ejs/jms/JMSConnectionHandle.invalidate(JMSConnectionHand
le.java:956)
4XESTACKTRACE          at
com/ibm/ejs/jms/JMSManagedConnection.cleanup(JMSManagedConnectio
n.java:1009)
4XESTACKTRACE          at
com/ibm/ejs/j2c/MCWrapper.cleanup(MCWrapper.java:1512)
4XESTACKTRACE          at
com/ibm/ejs/j2c/FreePool.cleanupAndDestroyMCWrapper(FreePool.jav
a:717)
4XESTACKTRACE          at
com/ibm/ejs/j2c/FreePool.returnToFreePool(FreePool.java:488)
4XESTACKTRACE          at
com/ibm/ejs/j2c/PoolManager.release(PoolManager.java:1816)
4XESTACKTRACE          at
com/ibm/ejs/j2c/MCWrapper.releaseToPoolManager(MCWrapper.java:23
54)
4XESTACKTRACE          at
com/ibm/ejs/j2c/MCWrapper.connectionErrorOccurred(MCWrapper.java
:2463)
4XESTACKTRACE          at
com/ibm/ejs/j2c/ConnectionEventListener.connectionErrorOccurred(
ConnectionEventListener.java:499)
4XESTACKTRACE          at
com/ibm/ejs/jms/JMSManagedConnection.connectionErrorOccurred(JMS
ManagedConnection.java:1447)
4XESTACKTRACE          at
com/ibm/ejs/jms/JMSManagedConnection.onException(JMSManagedConne
ction.java:1332)


The "More information about this page" link for WebSphere MQ
messaging provider activation specifications advanced
properties incorrectly points to information about WebSphere
MQ messaging provider connection factories.

Problem conclusion

This APAR resolves the above runtime issues that can be
experienced when using WebSphere MQ as a messaging provider.

Temporary fix

Comments

APAR Information

APAR number
PK79362
Reported component name
PLAT MSG COM
Reported component ID
620800101
Reported release
300
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-01-26
Closed date
2009-02-27
Last modified date
2009-03-03

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
620800101

Applicable component levels

R300 PSY
UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
25 October 2021

Tips

PK79362: Runtime problems using the WebSphere MQ messaging provider in WebSphere Application Server.

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

R300 PSY

Document Information

Share your feedback

Need support?