Troubleshooting
Problem
JMS destination based security option is used with OMS SDF services. At runtime, the JMS connection failed due to user authentication even the correct mq user and password are used.
Symptom
The OMS log has the following errors:
JMSCMQ0001: IBM MQ call failed with compcode '2' ('MQCC_FAILED') reason '2035' ('MQRC_NOT_AUTHORIZED').
or
JMSWMQ2013: The security authentication was not valid that was supplied for queue manager 'OM_QMGR' with
connection mode 'Client' and host name 'xxx(1414)'.
Cause
According to MQ v9.2 document:
Applications that use the IBM MQ classes for JMS might be affected by the change to the default authentication mode in IBM MQ 9.2.1. After upgrading the IBM MQ classes for JMS to IBM MQ 9.2.1, applications that previously used compatibility mode by default will use MQCSP authentication instead. This might cause applications that previously connected successfully to a queue manager to fail to connect with a JMSException containing reason code 2035 (MQRC_NOT_AUTHORIZED). If this occurs, use one of the methods described in Choosing the authentication mode to specify that the application uses compatibility mode.
Resolving The Problem
Add the following JVM parameter to solve this issue:
-Dcom.ibm.mq.cfg.jmqi.useMQCSPauthentication=N
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SS6PEW","label":"IBM Sterling Order Management"},"ARM Category":[{"code":"a8m0z000000cy00AAA","label":"Orders"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.0.0"}]
Was this topic helpful?
Document Information
Modified date:
18 September 2024
UID
ibm17168887