WebSphere Process Server messages     Operating Systems: All supported

ADML

ADML0000I: The server initialization is complete. The process ID is: {0}
Problem This informational message indicates that the server process started successfully.
User response No user action is required.
ADML0003E: A configuration error occurred in the ProcessDef Umask property {0}.
Problem The value of the Umask property is not in a valid integer format.
User response Edit the configuration and change the value of the process Umask property.
ADML0004E: An exception occurred when attempting to expand variable {0} {1}.
Problem The variable in the configuration data cannot be resolved.
User response Edit the configuration and change the value of the property to use a variable that can be resolved.
ADML0005I: The ${USER_INSTALL_ROOT} variable is missing; the tool is using ${WAS_INSTALL_ROOT} as a default.
Problem The ${USER_INSTALL_ROOT} variable is not set in the configuration files.
User response Edit the configuration and provide a ${USER_INSTALL_ROOT} variable.
ADML0006E: The ${WAS_INSTALL_ROOT} variable is missing.
Problem The variable setting for ${WAS_INSTALL_ROOT} value is missing. This variable is required.
User response Edit the configuration and provide a ${WAS_INSTALL_ROOT} variable.
ADML0008W: An unsupported platform type is encountered: {0} {1}
Problem The program is starting on an operating system platform that is not supported.
User response Do not attempt to run the program on this platform.
ADML0009E: An exception occurred waiting for server initialization {0}.
Problem An error occurred while waiting for the status socket of the process.
User response Record and save the exception information in this message for problem determination. See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.
ADML0011E: The server launched, but failed initialization. See the server log files for failure information.
Problem The server failed to run.
User response Look in the log files for the server to find information for problem determination. See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.
ADML0012E: An exception occurred when attempting to get a free port for status socket {0}.
Problem An error occurred when attempting to bind to a socket for server status. The socket might be in use.
User response See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.
ADML0018I: The log is generated.
Problem This informational message indicates progress of the program.
User response No user action is required.
ADML0019E: An exception occurred waiting for the server stop {0}.
Problem An error occurred during the processing of a stop request.
User response See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.
ADML0029E: No configuration is defined for server: {0}
Problem An attempt was made to start a server that has no configuration.
User response Verify that the server name is correct. If the server name is correct, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.
ADML0031E: The value specified in the ExecutableTargetKind property {0} is not valid.
Problem The value of the ExecutableTargetKind property is not valid.
User response Edit the configuration and change the value of the ExecutableTargetKind property to a valid value.
ADML0040E: The process timed out waiting for server "{0}" initialization: {1} seconds
Problem The server initialization process exceeded the timeout limit.
User response See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.
ADML0056E: The tool is unable to initiate monitoring for process {0} with PID {1} because of exception: {2}
Problem The node agent failed to establish a connection to the launched process.
User response Record and save the exception information in this message for problem determination.
ADML0057E: An error occurred while running file synchronization.
Problem The node agent failed to run the file synchronization.
User response Check the SystemOut.log file to see the detailed error.
ADML0058E: An error occurred while stopping the node.
Problem The node agent failed to stop the local application servers or itself.
User response Check the SystemOut.log file to see the detailed error.
ADML0059E: An error occurred restarting the node agent: {0}
Problem The node agent failed to restart itself.
User response Stop and start the node agent using the command-line utilities.
ADML0060W: The tool cannot contact server "{0}".
Problem The node agent failed to contact the server and assumed that the server is malfunctioning. The given server restarts if the "autoRestart" attribute is set to "true" in its monitoring policy, which is defined in the server.xml file.
User response Check the SystemOut.log file for this server. Normally, the log file shows why the given server cannot respond to the node agent. In case "autoRestart" is set to true, check to see whether it is restarted by the node agent.
ADML0061E: An error occurred during synchronization. Set the synchOnServerStartup value to false, if you want to proceed without synchronization.
Problem The node agent tried to do file synchronization before launching the process, but it failed.
User response Set the synchOnServerStartup value to false if you want to proceed without synchronization.
ADML0062W: The tool cannot load the server.xml file for server {0}.
Problem The node agent failed to load the server.xml file to read the monitoring policy for a given server.
User response Open the problem server.xml file to check for XML syntax errors.
ADML0063W: The tool cannot contact server "{0}". Force stop this server if it is still running.
Problem The node agent failed to contact the given server and assumed that the server is malfunctioning. The server restarts if the"autoRestart" attribute is set to "true" in its monitoring policy, which is defined in the server.xml file.
User response Check the SystemOut.log file for this server. Normally, the log file shows why the name of the server cannot respond to the node agent. In case "autoRestart" is set to true, check to see whether the node agent restarted the server.
ADML0064I: Restarting an unreachable server "{0}".
Problem This information message indicates the program status.
User response No user action is required.
ADML0065W: A sync operation prior to starting an application server failed.
Problem The node agent could not perform a sync operation before starting an application server. The dmgr may not be running or may be unavailable. The application server will still be started.
User response If you require a sync operation to be performed for the server's configuration, then ensure that the dmgr is up and running before another sync operation is invoked.
ADML0111E: A request to stop the server stop failed to complete.
Problem The server did not return a status indicating that it completed shutdown in response to a stop request.
User response Examine the server log files to see if an exception occurred during the stop logic that might have prevented a successful shutdown.
ADML0115I: The trace mode is on. The trace output is directed to: {0}
Problem This informational message indicates that the trace data is stored into a file.
User response No user action is required.
ADML0220I: The base server run time initialized; the tool is waiting for application initialization.
Problem This informational message indicates the progress of the program.
User response No user action is required.
ADML0523E: An error occurred trying to get the object name of server {0}.: {1}
Problem The query for the Server MBean failed and resulted in an exception.
User response Record and save the exception information in this message. Check the spelling of the server name.
ADML3000E: The tool is unable to locate the systemlaunch.properties file: {0}
Problem The systemlaunch.properties file contains default settings for important system properties. This file is required for server launching.
User response Verify that the file is available and can be read. See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.
ADML3001W: The {0} property is missing from the systemlaunch.properties file.
Problem A required property cannot be located in the system.properties file.
User response Edit the file and add the required property, along with a value for that property.
Reference topic    

Terms of Use | Feedback

Last updated: Jun 13, 2009 1:00:35 PM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.ws.management.resources.launcher.html

© Copyright IBM Corporation 2006, 2009. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)