Breadcrumb(); > Message Index (by Number) (by Subsystem) > EmbeddedLDAP Subsystem Messages

EmbeddedLDAP Subsystem Messages

The EmbeddedLDAP1.0 catalog contains messages in the range 171500 - 171999. Messages in this catalog are part of the weblogic.ldap Internationalization package and the weblogic.ldap Localization package. 171500 Error: The embedded LDAP Configuration file: fileName was not found and the embedded LDAP server has not been started. To resolve the problem, ensure that weblogic.home is defined correctly (it should have a lib subdirectory that contains this file). Description The lib directory contains the configuration files required for the embedded LDAP server. If those files are missing or the appropriate directory cannot be found, then the embedded LDAP server cannot initialize. Cause The embedded LDAP server cannot find the specified file. This file is installed as part of the installation process. Most likely, the default directory is not the server root directory and the lib subdirectory cannot be found. Action Set the default directory to the server root directory or set the location of the embedded LDAP server configuration files via the weblogic.EmbeddedLDAPConfigDirectory system property. 171501(retired) Error: The embedded LDAP replicas file: filename could not be loaded. The underlying exception was message. 171502(retired) Error: Could not set the listen address in the embedded LDAP MBean for the Admin server. Without the Listen address, the embedded LDAP server may not receive replicated updates from the master embedded LDAP server. The underlying exception was message. 171503 Error: The Listen address for the Admin server is obtained from either the Server MBean, the ServerRuntime MBean, or the URL specified by the weblogic.management.server command-line property. None of these returned a Listen address. Description The Listen address for the Admin server is required so that the replicated LDAP servers can receive changes from the master LDAP server that runs on the Admin server. If the Listen address for the Admin server is null, replication may not occur. Cause The Listen address is null. Action Check to see if the Listen address for the Admin server is defined in either the Server MBean, the ServerRuntime MBean, or the URL specified by the weblogic.management.server command-line property. 171504(retired) Error: Could not set the Listen address in the embedded LDAP MBean for a particular server. Without the Listen address, other Managed servers cannot use the replicated embedded LDAP server on the Managed server. The underlying exception was message. 171505(retired) Warning: Could not get Listen address for replicated embedded LDAP for server serverName. The Listen address for a replicated embedded LDAP server is obtained from either the Server MBean, the ServerRuntime MBean, or the EmbeddedLDAPReplicas.dat file. None of these returned a Listen address. 171506(retired) Error: The Embedded LDAP replicas file: filename was not found. When running via Managed Server Independence, this file is required to find the Listen address of any replicated embedded LDAP servers. 171507 Error: The Embedded LDAP Replicas file: filename could not be written. The underlying exception was message. Description The embedded LDAP server stores replica information in the file filename. This file could not be written because of an exception. Cause An exception occurred when saving the replica properties to the replicas file. Action Verify that the file message can be written to. Read the exception text for more information in diagnosing the problem. 171508(retired) Notice: Embedded LDAP binding on port port 171509(retired) Notice: Embedded LDAP binding on port port, listen address listenAddress 171510(retired) Info: Replication to the embedded LDAP server for server serverName will not occur until the server boots for the first time. 171511(retired) Info: Failover to the embedded LDAP server for server serverName has been disable since the Listen address cannot be determined. 171512 Critical: When attempting to cleanup after a failed embedded LDAP replica initialization, the file fileName could not be deleted. The directoryName directory and all its files MUST be deleted manually. Description The embedded LDAP server initializes a new replica in a Managed server by downloading a new replica from the Admin server and then importing it into the local replicated LDAP server. If this process fails, the embedded LDAP server attempts to cleanup and delete the local files. However, file fileName could not be deleted. The directoryName directory and all its files MUST be deleted manually. Cause It is not always possible to delete files that are open by a process. Action Delete the directoryName directory and all its files manually using the appropriate command for the operating system on which WebLogic server runs. 171513 Critical: Could not schedule trigger used for Embedded LDAP timer activities. The underlying exception was message. Description The Embedded LDAP server uses a trigger to perform periodic cleanup operations. The trigger could not be scheduled due to an exception. Cause A TimeTrigger exception was thrown when scheduling the trigger. Action Read the exception text in message for more information in diagnosing the problem. 171514(retired) Warning: Replica status validation failed. Reinitializing replica. The underlying exception was message. 171515(retired) Error: Failed to save configuration changes to the configuration repository after generating the credential for the embedded LDAP server - th. Description The credential for the embedded LDAP server will be lost and Managed servers may experience problems with the WebLogic Authentication and Authorization providers if the Admin server is restarted. Cause An exception was thrown in the call to save the domain. Action Ensure that the OS user which starts the server has authorization to write to the config.xml file. Optionally, you can set the credential for the embedded LDAP server via the Administration Console. 171516(retired) Error: Could not get exclusive access to the embedded LDAP data files directory: dir Description An embedded LDAP server is already using this directory. Since in memory data structures are used, two embedded LDAP servers cannot run at the same time in the same directory. Cause An exclusive lock for the directory dir could not be obtained because another WebLogic Server is already using this directory. Action Ensure that the first WebLogic Server is shutdown. 171517 Critical: An error occurred while attempting to get exclusive access to the embedded LDAP data files directory - dir. The exception thrown is th. Description WebLogic Server attempts to exclusively lock a file in the embedded LDAP server data file directory. When attempting to lock this file, an exception occurred. Cause An exclusive lock for the directory dir could not be obtained because an exception occurred. Action Investigate the associated exception and attempt to determine why the exclusive lock failed. 171518 Info: The following exception has occurred: \n Description A stack trace is being printed for an exception that occurred. Cause An error condition has occurred. Action Read the associated exception in the log. In general, a stack trace will help when debugging an existing problem. 171519 Error: Could not obtain an exclusive lock to the embedded LDAP data files directory: dir because another WebLogic Server is already using this directory. Ensure that the first WebLogic Server is completely shutdown and restart the server. Description An embedded LDAP server is already using this directory. Since in memory data structures are used, two embedded LDAP servers cannot run at the same time in the same directory. Cause An exclusive lock for the directory dir could not be obtained because another WebLogic Server is already using this directory. Action Ensure that the first WebLogic Server is shutdown and try rebooting the server. 171520 Warning: Could not obtain an exclusive lock for directory: dir. Waiting for sleepTime seconds and then retrying in case existing WebLogic Server is still shutting down. Description An embedded LDAP server is already using this directory. Since in memory data structures are used, two embedded LDAP servers cannot run at the same time in the same directory. WebLogic Server will wait for sleepTime seconds and retry to get the exclusive lock just in case the other WebLogic Server is still shutting down. Cause An exclusive lock for the directory dir could not be obtained because another WebLogic Server is already using this directory. Action If the server eventually boots, then ignore this warning as the lock was obtained. If the server fails to boot, ensure that the first WebLogic Server is shutdown and try rebooting the server. 171521 Critical: An error occurred while initializing the Embedded LDAP Server. The exception thrown is th. This may indicate a problem with the data files for the Embedded LDAP Server. This managed server has a replica of the data contained on the Master Embedded LDAP Server in the Admin server. This replica has been marked invalid and will be refreshed on the next boot of the managed server. Retry the reboot of this server. Description An exception was thrown when initializing the Embedded LDAP server. The initialization failed and the server cannot boot. Cause There may be a problem with either the Embedded LDAP server configuration files or the data files. Action Investigate the associated exception and attempt to determine why the exception occurred. Retry the reboot of the server and see if the refresh of the replica data files solves the problem. 171522 Critical: An error occurred while initializing the Embedded LDAP Server. The exception thrown is th. This may indicate a problem with the data files for the Embedded LDAP Server. If the problem is with the data files and it can not be corrected, backups of previous versions of the data files exist in dir. Description An exception was thrown when initializing the Embedded LDAP server. The initialization failed and the server cannot boot. Cause There may be a problem with either the Embedded LDAP server configuration files or the data files. Action Investigate the associated exception and attempt to determine why the exception occurred. Retry the reboot of the server. 171523 Error: Embedded LDAP Server Credential Unavailable: A credential value must be supplied for the Embedded LDAP configuration Description The Credential attribute of the Embedded LDAP MBean is null or a zero-length byte array. Cause The Credential attribute is invalid. Action Set the Credential attribute for the Embedded LDAP server configuration. 171524 Error: Cannot determine the Listen address for the Admin server. The Admin server URI uri obtained from either the Server MBean, the ServerRuntime MBean, or the URL specified by the weblogic.management.server command-line property has invalid syntax. Description The Listen address for the Admin server is required so that the replicated LDAP servers can receive changes from the master LDAP server that runs on the Admin server. If the Listen address for the Admin server is not determined, replication may not occur. Cause The Admin server URI has invalid syntax. Action Make sure a valid Listen address for the Admin server is defined in either the Server MBean, the ServerRuntime MBean, or the URL specified by the weblogic.management.server command-line property. 171525 Error: Error loading initial replica file. Check EmbeddedLDAP log for more details. Description Error loading initial replica file. Check EmbeddedLDAP log for more details. Cause An error occurred during the loading of the initial replica file. Action Check EmbeddedLDAP log for more details. 171526 Notice: Error loading initial replica file, attempting reload. Description An error occurred during the loading of the initial replica file. The initial replica file will be loaded again. Cause An error occurred during the loading of the initial replica file. Action None. The initial replica file will be loaded again. 171527 Notice: Added all LDAP entries successfully for initial replica. Description The reload of the initial replica file was a success. Cause An error occurred during the initial loading of the replica file. Action None. The reload of the initial replica file was successful.