Troubleshooting
Problem
Applications fail when using the IBM® WebSphere® MQ resource adapter with an authentication alias on an activation specification.
Symptom
Applications that connect to WebSphere MQ and have defined an authentication alias fail to start. Information such as the following, which contains the ClassNotFoundException exception, might occur in the SystemOut.log file:
| WSVR0501E: Error creating component com.ibm.ws.runtime.component.CompositionUnitMgrImpl@198c198c com.ibm.ws.exception.RuntimeWarning: javax.resource.ResourceException: com.ibm.ws.security.auth.j2c.WSDefaultPrincipalMapping ... Caused by: java.lang.ClassNotFoundException: com.ibm.ws.security.auth.j2c.WSDefaultPrincipalMapping |
Resolving The Problem
Although this problem prevents you from passing specific user identifiers and passwords when the application connects to WebSphere MQ, you can enable connections by either of the following actions:
- Ensure that the user ID under which the application server is running is a member of the mqm group on the WebSphere MQ queue manager host.
- Set the MCAUSER identifier on the SVRCONN channel in the WebSphere MQ queue manager to which the application is connecting.
Note: Both of these actions are temporary workarounds. If you require a secure environment, use Secure Sockets Layer (SSL).
Related Information
[{"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Java 2 Connectivity (J2C)","Platform":[{"code":"PF033","label":"Windows"}],"Version":"7.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21318595