Fixes are available
8.5.5.1: WebSphere Application Server V8.5.5 Fix Pack 1
8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
APAR status
Closed as program error.
Error description
Java cores show producer threads are blocked by a thread which invokes: com/ibm/ws/sib/api/jmsra/impl/JmsJcaManagedConnectionFactoryImpl .createManagedConnection()
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server Liberty profile * **************************************************************** * PROBLEM DESCRIPTION: JMS Connection pooling does not happen * * when clients running on a Liberty * * profile server try to access a remote * * messaging engine. * **************************************************************** * RECOMMENDATION: * **************************************************************** JMS Connection pooling does not happen when clients running on a Liberty profile server try to access a remote messaging engine. This may cause hang in some scenarios and the java core will show producer threads are blocked by a thread which invokes: com/ibm/ws/sib/api/jmsra/impl/JmsJcaManagedConnectionFactoryImpl .createManagedConnection()
Problem conclusion
The comparison logic was fixed to compare the requested connection and pooled connection The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.1. 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
PM95564
Reported component name
WAS LIBERTY COR
Reported component ID
5725L2900
Reported release
855
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2013-08-21
Closed date
2013-10-16
Last modified date
2013-10-16
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
WAS LIBERTY COR
Fixed component ID
5725L2900
Applicable component levels
R855 PSY
UP
Document Information
Modified date:
11 January 2022