If problems with LDAP Server plug-ins are detected, the following error messages are issued during Access Manager initialization. To log these messages to the catalina.out file, set the application component file logger to the warning level or higher.
Cause: The java.lang.Class.forName() method failed to load the LDAP Store Plugin class.
Action: Verify that a valid Java class file is available in Access Manager's class path for the referenced plug-in class file. Check the modifications you made to the web.xml file (see Step 2).
Cause: The java.lang.Class.newInstance() method failed to instantiate the LDAP Store Plug-in class.
Action: Verify that a valid Java class file is available in Access Manager's class path for the referenced plug-in class file. Also, ensure that the LDAP Store Plug-in has a zero parameter constructor.
Cause: A user store was configured with an unrecognized directory type. The configuration was manually modified to include an invalid directory type specifier or the configuration has been corrupted.
Action: Examine the supplied error detail and take applicable actions. If the directory type is wrong, reconfigure the user store with the correct directory type. If the configuration is corrupted, delete the user store configuration, then re-create it.