Fixes are available
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
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
APAR status
Closed as program error.
Error description
Fix several usability issues that have been found within the JMS feature.These include: . 1) Messaging flows should ignore the Bus Name, because there is no Bus concept in Websphere Application Server Liberty Profile. 2) Rectify the jmsMajorVersion and jmsMinorVersion in JMS-Connection metadata. 3) Print high-message threshold in logs when queue's max depth have been reached. 4) User-name must be printed in logs when there is an authentication failure. 5) Remov duplicate CWSID0122I messages in logs when messaging engine id is not provided in the server configuration file. 6) Rename "WebSphere Embedded Queue Connection Factory" to "Embedded Messaging" and in the same way for Topic Connection factory and Connection Factory 7) Prevent destination UUID's from being printed in the logs when a destination is deleted. 8) Fix NullPointerException when wasJmsServer-1.0 feature is removed. 9) Remove irrelevant messages like CWSIP0181W and CWSIU0006I from appearing in logs when a RECEIVE operation is being performed in queue.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server Liberty Profile * **************************************************************** * PROBLEM DESCRIPTION: Fix several usability issues for JMS * * feature * **************************************************************** * RECOMMENDATION: * **************************************************************** Fix several usability issues: 1) Messaging flows should ignore the Bus Name, because there is no Bus concept in Websphere Application Server Liberty Profile. 2) Rectify the jmsMajorVersion and jmsMinorVersion in JMS-Connection metadata. 3) Print high-message threshold in logs when queue's max depth have been reached. 4) User-name must be printed in logs when there is an authentication failure. 5) Remov duplicate CWSID0122I messages in logs when messaging engine id is not provided in the server configuration file. 6) Rename "WebSphere Embedded Queue Connection Factory" to "Embedded Messaging" and in the same way for Topic Connection factory and Connection Factory 7) Prevent destination UUID's from being printed in the logs when a destination is deleted. 8) Fix NullPointerException when wasJmsServer-1.0 feature is removed. 9) Remove irrelevant messages like CWSIP0181W and CWSIU0006I from appearing in logs when a RECEIVE operation is being performed in queue.
Problem conclusion
All the usability issues reported are fixed. The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.4. 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
PI28473
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
2014-10-28
Closed date
2014-10-29
Last modified date
2014-11-11
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:
28 April 2022