Troubleshooting
Problem
In IBM WebSphere Application Server, MDB Listener fails to start with the following exception in the logs:
[][10/16/15 3:10:46:167 EDT] 00000021 MDBListenerIm W WMSG0019E: Unable
to start MDB Listener MessageDetectorMDB, JMSDestination
jms/myQueue : java.security.PrivilegedActionException:
javax.security.auth.login.LoginException: No LoginModules configured for
at
com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.
java:122)
at com.ibm.ejs.jms.listener.MDBListenerImpl.createResources(MDBListenerImpl.java:367)
at com.ibm.ejs.jms.listener.MDBListenerImpl.internalStart(MDBListenerImpl.java:727)
Caused by: javax.security.auth.login.LoginException: No LoginModules configured for
at javax.security.auth.login.LoginContext.init(LoginContext.java:256)
at javax.security.auth.login.LoginContext.
]
Cause
This exception could occur if the Mapping-configuration alias or container managed authentication alias on the QCF configuration page is not specified.
Resolving The Problem
Ensure that the following configurations are completed on the queue connection factory settings panel in the administrative console.
Configure the "Mapping-configuration alias" in the Queue connection factory settings page for jms/myQueue to be "DefaultPrincipalMapping".
Another cause of this problem could be that the Java Message Service QCF jms/myQueue is not associated with a J2C authentication alias. To fix this, in the same QCF settings panel, set the container-managed and component-managed authentication aliases to the correct value.
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21326495