Fixes are available
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
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
A JMS application connected to WebSphere Application Server v7.0.x Service Integration Bus Messaging Engine terminates abnormally and following errors occured On the server hosting the application: CWSIC8007E: An exception was caught from the remote server with Probe Id 3-004-0013. Exception: CWSIC2059E: An internal error occurred. An attempt was made to get an object from the map with id #, but there is no item in the map with this key.. On the server hosting the messaging engine Several FFDCS are written with the following errors: com.ibm.websphere.sib.exception.SIErrorException: CWSIC2059E An internal error occurred. An attempt was made to get an object from the map with id #, but there is no item in the map with this key. com.ibm.ws.sib.msgstore.XidStillAssociatedException: CWSIS1008E: rollback(XID) not possible as the supplied XID has not yet been called to end it's association with the messaging engine. XID:nnnn com.ibm.ws.sib.msgstore.XidUnknownException: CWSIS1007E:: rollback(XID) not possible as the supplied XID is not recognised by the messaging engine. XID:mmmmm
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of the default messaging provider * * for * * IBM WebSphere Application Server * **************************************************************** * PROBLEM DESCRIPTION: A JMS application running in a * * managed environment that is * * connecting to a messaging enigne in a * * remote process may experience multiple * * exceptions such as CWSIC2059E, * * CWSIS1008E and CWSIS1107E. * **************************************************************** * RECOMMENDATION: * **************************************************************** When a JMS Connection is created an initial connection to the messaging engine is established, when a JMS Session is created from that JMS connection a clone of that initial connection is created. When the application caches the JMS Connection there is a chance that the underlying connection needs to be recreated due to a network issue or destroying of the connection from the connection pool. The JMS Session is then created with a new connection that could potentially be on a different physical socket to the connection created under the JMS Connection. This event leads to the exceptions below: - CWSIC2059E - CWSIS1008E - CWSIS1007E In order to encounter this APAR the application must be running in a managed environment (EJB container, web container etc) and must be making a remote connection to a messaging engine within a different JVM.
Problem conclusion
This APAR solves the problem and ensures that the messaging engine connection associated with the JMS Connection is updated if a new connection is created on a different physical socket. The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.21 and 8.0.0.2. 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
PM38672
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
2011-05-09
Closed date
2011-08-24
Last modified date
2011-08-24
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
PM54264
Fix information
Fixed component name
PLAT MSG COM
Fixed component ID
620800101
Applicable component levels
R300 PSY
UP
R800 PSY
UP
Document Information
Modified date:
27 October 2021