Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The kernel has been started. The interval (in seconds) is relative to when the platform was launched. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | A server installation could not be found at a specified location. |
Action | Reinstall or repair the Liberty profile. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | An issue was encountered that prevented the runtime environment from being launched. |
Action | Review the available logs to identify the issue and resolve it. |
Explanation | Object Request Broker (ORB) support requires the orb feature. |
Action | Enable the orb feature to enable ORB support. |
Explanation | There is an error in the URI for the specified bootstrap properties file. |
Action | Correct the URI for the bootstrap properties then retry the command. |
Explanation | The server.xml file cannot be read or does not exist. |
Action | Ensure that the server.xml file exists and can be read by the current user. |
Explanation | A required argument was not supplied. |
Action | Supply the correct argument then retry the command. Try using --help for a description of the arguments for the supplied option. |
Explanation | A character that is not valid has been used in the server name. |
Action | Rename the server using only valid characters: Unicode alphanumeric (e.g. 0-9, a-z, A-Z), underscore (_), dash (-), plus (+), and period (.). |
Explanation | The specified option was not recognized. |
Action | Retry the command using valid options. Try using --help for a list of valid options. |
Explanation | The bootstrap.properties file cannot be read or does not exist. |
Action | Ensure that the specified file exists and can be read by the current user. |
Explanation | At least one exception was encountered while installing or starting the server. |
Action | Check that the product has been installed correctly. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The Java 2 Security permissions are insufficient for the bootstrap JAR file to launch the runtime environment and the OSGi framework. |
Action | Ensure that the bootstrap JAR file has been granted AllPermission privileges in the Java 2 Security policy file. |
Explanation | The JAVA_HOME system variable is set to point to a version of Java that is 31-bit. |
Action | Adjust the JAVA_HOME system variable to point to 64-bit Java 6 or higher. |
Explanation | The exception prevented the launch of the server. |
Action | Resolve the exception, if possible, then retry the action. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The server installation is missing required files and the server could not start. |
Action | Check that the product has been installed correctly. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The framework definition file was not found. |
Action | Ensure that the framework definition resource exists and can be read by the current user. |
Explanation | The specified framework bundle artifact could not be found. |
Action | Ensure that the resource exists and can be read by the current user. |
Explanation | The server installation is missing required files and the server could not start. |
Action | Check that the product has been installed correctly. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The specified kernel definition could not be found. |
Action | Ensure that the kernel definition resource exists and can be read by the current user. |
Explanation | The supplied location refers to an existing file instead of a directory. |
Action | Change the specified location to a directory then retry the action. |
Explanation | The specified platform cache file could not be written. |
Action | Check and resolve the exception, then retry the action. |
Explanation | You may specify only one server on the command line. The first server name has been processed; the remaining names have been ignored. |
Action | No action is required. Specify only one server to avoid this warning. |
Explanation | You are trying to start a server that is already running. |
Action | Stop the existing server instance before trying to start the server, or start a different server. |
Explanation | The specified server could not be created. |
Action | Check and resolve the exception, then try again to create the server. |
Explanation | The specified server does not exist, so no action can be performed on it. |
Action | Check the name of the server, or create a server with the specified name, then retry the command. |
Explanation | At least one exception was encountered while installing the platform bundles. |
Action | Review the logs to identify and resolve the exceptions, then try again to install the bundles. |
Explanation | One or more platform bundles could not be found. |
Action | Ensure that the platform resources exist and can be read by the current user. |
Explanation | The installation image might be incomplete. |
Action | Verify the installation then try again to install the bundles. |
Explanation | The location of the initial log file was not specified correctly, or the file was not readable. |
Action | Check the location and state of the initial log file. |
Explanation | The kernel has stopped after the specified interval (in seconds). This interval is relative to when the platform was launched. |
Action | No action is required. |
Explanation | The specified protocol is not supported, so the system uses the default protocol (telnet) instead. |
Action | No action is required to use the default protocol. Otherwise, modify the configuration to use a supported protocol. |
Explanation | The server installation is missing required files and the server could not start. |
Action | Check that the product has been installed correctly. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The specified log provider resource could not be found. |
Action | Ensure that the log provider resource exists and can be read by the current user. |
Explanation | The platform bundles could not be resolved against the platform cache. This problem can normally be resolved with a clean restart. |
Action | Restart the server using the --clean option to clear the cache. |
Explanation | The framework has been restarted because the platform cache was out of sync. |
Action | No action is required. |
Explanation | Either an unsupported Java version is running, or the JAVA_HOME system variable is set to point to an older version of Java. |
Action | Upgrade the Java version to Java 6, or adjust the JAVA_HOME system variable to point to Java 6. |
Explanation | The runtime environment must be launched from a local file, for example a JAR file. |
Action | Verify that the command being used is using the command java -jar <localJarFile> to launch the runtime environment. |
Explanation | The server directory must be writable in order to start the server. |
Action | Verify that you have write access to the server directory and workarea. |
Explanation | The server directory must not already exist when creating a server. |
Action | Either choose a new server name or delete the directory, then rerun the command. |
Explanation | The function requested requires the Java Attach API, and an implementation could not be found. |
Action | Specify the location of the Java Attach API on the CLASSPATH. |
Explanation | The specified exception prevented the process control agent from running correctly. |
Action | Resolve the exception then retry the action. |
Explanation | The process control agent could not find a running instance of the specified server. |
Action | Check that an instance of the specified server is running, and that it is running under the same JRE implementation. |
Explanation | A running instance of the specified server was found, but it did not shut down properly in response to a stop command. |
Action | Review the server logs for more information about why the server did not shut down properly. |
Explanation | The directory does not exist or is not readable. |
Action | Review the configuration. |
Explanation | Could not package the specified server. |
Action | Review the server logs for more information. If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An unexpected exception occurred when initializing the server command listener. |
Action | Review the server logs for more information about why the command failed. If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The command was ignored because it was not recognized. |
Action | Use the help action to verify you are attempting a valid command with valid options. If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | A FileNotFoundException exception occurred when trying to open the file. |
Action | Check that the path exists, and you have write access and sufficient disk space. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | An IOException occurred. |
Action | Retry the operation. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The option was ignored because it was not recognized. |
Action | Retry the command using valid options. Try using --help for a list of valid options. |
Explanation | An IO exception occurred. |
Action | Retry the operation. If the error still persists, report the problem to IBM service. |
Explanation | A iFix jar has been found, but the base jar the iFix applies to has not been installed. |
Action | Obtain an iFix for the fixpack level installed, or update to the appropriate fixpack level, or delete the iFix jar. |
Explanation | Text files are not tagged with the specified encoding. |
Action | The file may need to be translated to the IBM-1047 encoding before being viewed with standard editors and text utilities. |
Explanation | Text files are not tagged with the specified encoding. |
Action | The file may need to be translated to the IBM-1047 encoding before being viewed with standard editors and text utilities. |
Explanation | Registration of the native method failed. |
Action | Check that the native method exists. |
Explanation | Unable to load z/OS native library. |
Action | Check that the path exists and retry. |
Explanation | The specified server cannot be created because another appplication was performing file operations in the new server directory. |
Action | Investigate why there was file activity in the server directory outside the create command then delete the server directory and try to create the server again. |
Explanation | The specified server cannot be created either because there was not enough space to create the server or because the location is prevented from being written to. |
Action | Ensure that there is enough disk space to create the server and ensure that the location can be written to then try again. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | A dump was requested, but the server JVM does not support the dump type. |
Action | No action is required. |
Explanation | Could not find the file or the file's format is wrong. |
Action | Ensure the file is existent and the file's format is correct. |
Explanation | An interim fix resource has been found, but the base resource that the interim fix applies to has not been installed. |
Action | Obtain an interim fix for the installed fix pack level, or update to the appropriate fix pack level, or delete the interim fix resource. |
Explanation | The specification string for the BLST file does not conform to the required syntax. The server is not started. |
Action | Specify the the symbolic-name and version-range of the BLST file in the form: <symbolic-name>;version="<version-range>". The symbolic-name must be a valid OSGi token. The version-range must be a valid OSGi version-range. Additionally, the version range must contain both an upper and lower bound, which may can be either inclusive or exclusive, and must not specify a qualifier. |
Explanation | The named BLST file could not be located. The server installation is missing required files and the server could not start. |
Action | Specify a resolvable BLST file in the server bootstrap.properties file of the server. |
Explanation | The platform directory could not be located. The server installation is missing required files and the server could not start. |
Action | Check that the product has been installed correctly. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The version range of the kernel could not be read. The server installation is missing required files and the server could not start. |
Action | Check that the product has been installed correctly. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The named server was unable to be queried to determine the features to retain during packaging. The resulting package archive may be invalid. |
Action | Check the named server is able to start, and reattempt the package. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The named server has been queried for currently configured features, but has not shutdown as requested. |
Action | Check the named server is able to start, and stop and reattempt the package operation. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The server is unable to be packaged with the options selected, as it was not possible to determine the configured features for the server. |
Action | Check the configuration for the server, and verify the server is able to start and stop. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The server could not be packaged, because the server manifest was missing. |
Action | Check that the product has been installed correctly. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The property could not be found within the specified property file. |
Action | Make sure that the property name exists and is spelled correctly. |
Explanation | The request to package the server with the requested operating system filter was prevented due to a missing resource. |
Action | Confirm if the server being packaged had the requested operating system content removed by a prior packaging operation that specified --include=minify. If so, retry the package on a server that has not been reduced by a previous package operation. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | An IOException occurred when packaging required Liberty content. |
Action | Retry the package operation on a freshly installed server. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The --os parameter is intended to be used in conjuction with --include=minify to specify which operating systems to support during a packaging operation. |
Action | Consult the documentation, and either remove the --os parameter from the command, or add --include=minify and retry the operation. |