|
Problem(Abstract) |
When trying to connect to an external WebSphere MQ Queue
Manager from an application within WebSphere Application Server, and the
Transport Type is set to BINDINGS, the following exception occurs :
javax.jms.JMSSecurityException: MQJMS2013: invalid security authentication
supplied for MQQueueManager
at
com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQXAQueueConnectionFactory.java:137)
at
com.ibm.ejs.jms.JMSManagedQueueConnection.createConnection(JMSManagedQueueConnection.java:157)
at
com.ibm.ejs.jms.JMSManagedConnection.<init>(JMSManagedConnection.java:163)
at
com.ibm.ejs.jms.JMSManagedQueueConnection.<init>(JMSManagedQueueConnection.java:64)
at
com.ibm.ejs.jms.WSJMSManagedQueueConnectionFactory.createManagedConnection(WSJMSManagedQueueConnectionFactory.java:84)
at
com.ibm.ejs.jms.JMSManagedConnectionFactory.createManagedConnection(JMSManagedConnectionFactory.java:469)
at
com.ibm.ejs.j2c.poolmanager.FreePool.createManagedConnectionWithMCWrapper(FreePool.java:1244)
at
com.ibm.ejs.j2c.poolmanager.FreePool.createOrWaitForConnection(FreePool.java:1030)
There are no other linked MQ messages. |
|
|
|
Cause |
The message associated with this specific exception stack
is thrown because the user trying to connect to the MQ Queue Manager is
not the user associated with the current running process. The WebSphere MQ
Queue Connection Factory (configured in WebSphere) obtained a user id and
password from a configured Component-managed Authentication Alias or a
Container-managed Authentication Alias. |
|
|
Resolving the
problem |
Make sure that the Component-managed Authentication Alias
and Container-managed Authentication alias fields of the WebSphere MQ
Queue Connection Factory are left blank, and that the user that starts
WebSphere is included in the MQM user group.
The problem can also be avoided by using the CLIENT transport type. In
this case, user permission is set on the channel.
|
|
|