Fixes are available
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
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
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11
APAR status
Closed as program error.
Error description
A JMS queue connection factory was configured to connect to WebSphere MQ and a container-managed authentication alias was specified but the mapping configuration alias was not set. The intended behaviour in this scenario is that the DefaultPrincipalMapping is used to map the authentication alias to the user ID and password, however the alias was not applied and the following message was generated in the SystemOut.log: J2CA0114W: No container-managed authentication alias found for ConnectionFactory or DataSource jms/XXXQCF. Typically this will result in the JMS application failing to connect to the JMS provider with MQRC_NOT_AUTHORIZED errors as userid/password passed to the JMS Provider is not that configured in the container-managed authentication alias specified for the JMS queue connection factory, an example of which is show below: MDBListenerIm W WMSG0019E: Unable to start MDB Listener XXX, JMSDestination jms/XXXQ : com.ibm.msg.client.jms.DetailedJMSSecurity Exception: JMSWMQ2008: Failed to open MQ queue 'XXXQ'. JMS attempted to perform an MQOPEN, but WebSphere MQ reported an error.Use the linked exception to determine the cause of this error. Check that the specified queue and queue manager are defined correctly. at com.ibm.msg.client.wmq.common.internal.Reason.reasonTo Exception(Reason.java:516) at com.ibm.msg.client.wmq.common.internal.Reason.create Exception(Reason.java:216) at com.ibm.msg.client.wmq.internal.WMQMessageConsumer.check JmqiCallSuccess(WMQMessageConsumer.java:124) at com.ibm.msg.client.wmq.internal.WMQConsumerShadow.initialize (WMQConsumerShadow.java:973) at com.ibm.msg.client.wmq.internal.WMQAsyncConsumerShadow. initialize(WMQAsyncConsumerShadow.java:846) at com.ibm.msg.client.wmq.internal.WMQConnectionBrowser. <init>(WMQConnectionBrowser.java:1359) at com.ibm.msg.client.wmq.internal.WMQConnection.create ConnectionBrowser(WMQConnection.java:835) Caused by: com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason ' 2035' ('MQRC_NOT_AUTHORIZED'). at com.ibm.msg.client.wmq.common.internal.Reason. createException(Reason.java:204)
Local fix
set the mappingConfigAlias to DefaultPrincipalMapping
Problem summary
**************************************************************** * USERS AFFECTED: WebSphere Application Server users of JMS * * Connection Factories * **************************************************************** * PROBLEM DESCRIPTION: Container-managed Authentication * * Alias not mapped using * * DefaultPrincipalMapping if mapping * * configuration alias not set. * **************************************************************** * RECOMMENDATION: * **************************************************************** If the mapping configuration alias is not set then the DefaultPrincipalMapping should be used to map the container-managed authentication alias. This is already the case for datasources, however for JMS Connection Factories the authentication alias was not applied when obtaining the connection.
Problem conclusion
The J2C component was modified so that the container-managed authentication configured for a JMS Connection Factory is mapped using the DefaultPrincipalMapping if the mapping configuration alias is not set. The fix for this APAR is currently targeted for inclusion in fix packs 8.5.5.13 and 9.0.0.6. 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
PI81163
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-05-05
Closed date
2017-09-05
Last modified date
2017-09-05
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
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R850 PSY
UP
Document Information
Modified date:
04 May 2022