APAR status
Closed as program error.
Error description
After the Queue Manager is restarted, the JMS listener port is
jammed resulting in a deadlock situation.
There seems to be a problem with the messagingImpl.jar file in
the classes directory.
Local fix
There seems to be a problem in the messagingImpl.jar file in the
classes directory. A new version of messagingImpl.jar was
created by Rohit Bhasin which has resolved this issue for the
customer.
Problem summary
****************************************************************
* USERS AFFECTED: This problem affects customers who use the *
* Java Message Service (JMS) functionality *
* provided with WebSphere Application Server *
* Version 5.02 and 5.1.1. *
****************************************************************
* PROBLEM DESCRIPTION: After a Queue Manager restart, the *
* following error messages appear in *
* the WebSphere Application Server *
* system log : *
* *
* JMSExceptionL E WMSG0018E: Error on *
* JMSConnection for MDB *
* merctopicMDBBean , JMSDestination *
* jms/MERC.JMS.TOPIC : *
* javax.jms.JMSException: MQJMS2002: *
* failed to get message from MQ queue *
* *
* at com.ibm.mq.jms.services. *
* ConfigEnvironment.newException *
* (ConfigEnvironment.java(Inlined *
* Compiled Code)) *
* at com.ibm.mq.jms.MQQueueAgentThread. *
* browse *
* (MQQueueAgentThread.java(Compiled *
* Code)) *
* at *
* com.ibm.mq.jms.MQQueueAgentThread.run *
* (MQQueueAgentThread.java(Compiled *
* Code)) *
* at *
* java.lang.Thread.run(Thread.java:568) *
****************************************************************
* RECOMMENDATION: *
****************************************************************
In this situation, we have two threads involved in a Deadlock
situation on a synchronised set within the code. As part of
the Listener shutdown process, the JMSManagedConnection code
locks a synchronised set which has a list of registered
connections event listeners. After obtaining a lock, the
JMSManagedConnection code calls in to our JCA code which in
turn tries to reference the already locked synchronised set.
Thus the two threads wait for each other in a deadlock.
Problem conclusion
To get around this problem, we create a copy of the
synchronised set and allow one thread to work on the copy of
the freeing the threads from a deadlock situation.
The fix for this APAR is currently targeted for inclusion in
Cumulative Fix 11 for WebSphere Application Server Version
5.0.2,
Cumulative Fix 5 for WebSphere Application Server Version
5.1.1.
and Cumulative Fix 2 for WebSphere Application Server Version
6.0.1. Please refer to the Recommended Updates page for
delivery
dates:
http://www-1.ibm.com/support/docview.wss?rs=180&context=SSEQTP
&uid=swg27004980
Temporary fix Comments
APAR information |
APAR number |
PK02976 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
10I |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2005-03-23 |
Closed date |
2005-05-19 |
Last modified date |
2005-05-26 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
|
Fix information |
Fixed component name |
WAS BASE 5.0 |
Fixed component ID |
5630A3600 |
Applicable component levels |
R003 PSY |
UP |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00P PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
R103 PSY |
UP |
R10A PSY |
UP |
R10H PSY |
UP |
R10I PSY |
UP |
R10P PSY |
UP |
R10S PSY |
UP |
R10W PSY |
UP |
|