Fixes are available
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
When a Messaging Engine attempts to establish a connection with another Messaging Engine in the same BUS, if an exception occurs at a critical point in the establishment of the connection, connection retry will stall and a connection between the messaging engines is never established. Messages will not flow between these messaging engines and may build up on transmission queues. An FFDC at one of the messaging engines' server will have the following stack frame: com.ibm.ws.sib.comms.server.mesupport.METransportReceiveListener .rcvTRMExchange(METransportReceiveListener.java...)
Local fix
Restart the messaging engine which issued the CWSIT0039E error.
Problem summary
**************************************************************** * USERS AFFECTED: Users of the default messaging provider for * * IBM WebSphere Application Server * **************************************************************** * PROBLEM DESCRIPTION: Connection retry logic for * * connections between messaging engines * * in the same BUS may stall. * **************************************************************** * RECOMMENDATION: To recover from this situation, without * * PM28508 applied, a restart of the messaging * * engine on the server where the FFDC is * * dumped is required. * **************************************************************** The problem resulted from state that was not cleaned up as a result of the Exception. Both messaging engines attempted to connect to each other, but only one connection was ever created. When this problem occured, the messaging engine on the server which dumped the FFDC believed that connection establishment was in progress and so did not attempt to initiate a connection to the other messaging engine. The messaging engine on which the FFDC was not dumped continued to retry the connection as per sib.trm.retry (default 30 seconds) but failed to establish a connection because it was told connection establishment was already in progress.
Problem conclusion
This APAR ensures that the state is cleaned up when an exception occurs at the critical point highlighted by this problem. The fix for this APAR is currently targeted for inclusion in fix pack 6.1.0.37 and 7.0.0.17. 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
PM28508
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
2010-12-08
Closed date
2011-02-07
Last modified date
2011-02-07
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
Document Information
Modified date:
27 October 2021