MBean cannot be used in initialization of WebSphere Application Server custom registry
 Technote (troubleshooting)
 
Problem(Abstract)
If you have created a custom registry, you cannot use an MBean within the registry initialization.
 
Symptom
Errors similar to the following will be seen in the SystemOut.log:


SECJ0373E: Cannot create credential for user <null> due to failed validation of the LTPA token. The exception is .
SECJ0222E: An Unexpected exception occurred when trying to create a LoginContext. The LoginModule alias is system.RMI_INBOUND...
 
Cause
The MBean will need security to be initialized as it will be needed for the MBean to start.
 
Resolving the problem
The custom registry should not depend on any IBM® WebSphere® Application Server internal resources. Therefore, MBeans cannot be used in initialization of a custom registry.
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Security
Operating system(s): Windows
Software version: 6.1
Software edition:
Reference #: 1231135
IBM Group: Software Group
Modified date: Feb 22, 2006