Express (Distributed operating systems), v8.0 > Reference > Messages
ADML
ADML0000I: The server initialization is complete. The process ID is: {0}, server name is: {1}
Explanation The server process started successfully. Action No user action is required.
ADML0003E: A configuration error occurred in the ProcessDef Umask property {0}.
Explanation The value of the Umask property is not in a valid integer format. The valid format is string containing the integer representation. Action Edit the configuration and change the value of the process Umask property.
ADML0004E: An exception occurred when attempting to expand variable {0} {1}.
Explanation The variable in the configuration data cannot be resolved. The variable may not exist or it may have the wrong value. Action Check variable.xml file in your WebSphere configuration to see make sure the variable exist and has the correct value. 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.
Explanation The ${USER_INSTALL_ROOT} variable is not set in the configuration files. Action Edit the configuration and provide a ${USER_INSTALL_ROOT} variable.
ADML0006E: The ${WAS_INSTALL_ROOT} variable is missing.
Explanation The variable setting for ${WAS_INSTALL_ROOT} value is missing. This variable is required. Action Edit the configuration and provide a ${WAS_INSTALL_ROOT} variable.
ADML0008W: An unsupported platform type is encountered: {0} {1}
Explanation The program is starting on an operating system platform that is not supported. Action Do not attempt to run the program on this platform.
ADML0009E: An exception occurred waiting for server initialization {0}.
Explanation An error occurred while waiting for the server to get initialized. The server socket may have been timeout. Action Examine the exception in this message for problem determination. Check the logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this error.
ADML0011E: The server launched, but failed initialization. See the server log files for failure information.
Explanation The server failed to run. Action Check the logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this error.
ADML0012E: An exception occurred when attempting to get a free port for status socket {0}.
Explanation The server status could not be obtained because the attempt to bind to a socket failed. The socket might be in use. Action Examine the exception in this message for problem determination. Check the logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this error. If the problem caused by socket in use, check with your network administrator how to solve this problem.
ADML0018I: The log is generated.
Explanation The program log was generated. Action No user action is required.
ADML0019E: An exception occurred waiting for the server stop {0}.
Explanation The server could not be stopped. Action Examine the exception in this message for problem determination. Check the logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this error.
ADML0029E: No configuration is defined for server: {0}
Explanation An attempt was made to start a server that has no configuration. Action Verify that the server name is correct.
ADML0031E: The value specified in the ExecutableTargetKind property {0} is not valid.
Explanation The value of the ExecutableTargetKind property is not valid. Action Select a valid ExecutableTargetKind such as Java class or jar. You may want to examine the exception in this message for problem determination. You could also check the logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this error.
ADML0040E: The process timed out waiting for server "{0}" initialization: {1} seconds
Explanation The server initialization process exceeded the timeout limit. Action Examine the exception in this message for problem determination. Check the logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this error.
ADML0056E: The tool is unable to initiate monitoring for process {0} with PID {1} because of exception: {2}
Explanation The nodeagent failed to establish a connection to the launched process. Action Check to make sure nodeagent is running, look at nodeagent logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this error.
ADML0057E: An error occurred while running file synchronization.
Explanation The nodeagent failed to run the file synchronization. Action Check the logs and trace to see the detailed error.
ADML0058E: An error occurred while stopping the node.
Explanation The nodeagent failed to stop the local application servers or itself. Action Examine the exception in this message for problem determination. Check the logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this error.
ADML0059E: An error occurred restarting the nodeagent: {0}
Explanation The nodeagent failed to restart itself. Action Stop and start the nodeagent by using the startNode or stopNode command-line utilities scripts.
ADML0060W: The tool cannot contact server "{0}". The server will not be restarted since Automatic Restart is false.
Explanation The node agent failed to contact the server. The server might be malfunctioning. The specified server restarts if the "autoRestart" attribute is set to "true" in the server monitoring policy, defined in the server.xml file. For this server, the "autoRestart" attribute is set to false. Action Check the logs and trace for this server. Usually, the logs show why the given server cannot respond to the node agent.
ADML0061E: An error occurred during synchronization. Set the synchOnServerStartup value to false, to proceed without synchronization.
Explanation The nodeagent tried to do file synchronization before launching the process, but the synchronization failed. Action Check to see the nodeagent is started without error by looking at nodeagent logs. Or set the synchOnServerStartup value to false to proceed without synchronization.
ADML0062W: The tool cannot load the server.xml file for server {0}.
Explanation The nodeagent failed to load the server.xml file to read the monitoring policy for a given server. Action 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.
Explanation The nodeagent failed to contact the given server. The server might be malfunctioning. The specified server can be restarted if the"autoRestart" attribute is set to "true" in the server monitoring policy, defined in the server.xml file. For restarting the server, the nodeagent must try to stop the server by calling the stop method on the process. If the stop does not complete, the nodeagent may also call the terminate method on the process. Action Check the logs and trace for this server. Normally, the logs show why the server cannot respond to the nodeagent. If the "autoRestart" attribute is set to true, check to see whether the nodeagent restarted the server.
ADML0064I: Restarting an unreachable server "{0}".
Explanation This information message indicates the program status. Action No user action is required.
ADML0065W: A sync operation prior to starting an application server failed.
Explanation The node agent started the application server, but could not first synchronize the configuration data of the node with the master copy of configuration data at the dmgr. The dmgr might not be running or might be unavailable. Action If you require synchronization for the server configuration, ensure that the dmgr is running before another synchronization occurs.
ADML0066I: The stop did not complete. The node agent is trying to end processing of server "{0}".
Explanation The node agent tried unsuccessfully to stop an application server. The node agent is trying the terminate method to force the server to end processing. Action Check the logs and trace for this server. Usually, the logs show why the server cannot respond to the node agent. See whether the node agent was able to terminate the process and restart the server.
ADML0067I: The initial heap size of {0} MB is larger than the maximum heap size of {1} MB. The server will use a maximum heap size that is the same value as the initial heap size.
Explanation The server will fail to start with an initial heap size that is greater than the maximum heap size. Action No action is necessary.
ADML0068I: Attempt {0} to restart an unreachable server "{1}" returned with the following status indicating whether the server was restarted successfully: {2}
Explanation Multiple attempts are made to restart an unreachable server. This message indicates the resulting status for one of these attempts. Action No user action is required.
ADML0111E: A request to stop the server stop failed to complete.
Explanation The server did not return a status indicating that it completed shutdown in response to a stop request. Action Examine the server logs and trace 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}
Explanation The trace data is stored in a file. Action No user action is required.
ADML0220I: The base server run time initialized; the tool is waiting for application initialization.
Explanation This informational message indicates the progress of the program. Action No user action is required.
ADML0523E: An error occurred trying to get the object name of server {0}.: {1}
Explanation The Server MBean could not be queried. The server name might be misspelled or the Server MBean might not run. Action Check the spelling of the server name. Examine the exception in this message for problem determination. Check the logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this error.
ADML3000E: The tool is unable to locate the systemlaunch.properties file: {0}
Explanation The systemlaunch.properties file contains default settings for important system properties. This file is required for server launching. Action Verify that the file is available and can be read.
ADML3001W: The {0} property is missing from the systemlaunch.properties file.
Explanation A required property cannot be located in the system.properties file. Action Edit the file and add the required property, along with a value for that property.