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 | While processing the specified file, an error occurred that prevented the system from converting from the EBCDIC format to ASCII. The EBCDIC version of the file remains intact. |
Action | Manually convert the file if you want to view it on an ASCII-based system. No action is required if this file will be processed by IBM 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 system is configured to request that Java dumps be taken and collected in the server dump archive. The requested Java dump cannot be found on the file system at the location indicated and will not be collected in the server dump archive. |
Action | Check the server logs, the console.log and messages.log, or both, to determine if the requested Java dumps are available at another location or determine why the Java dump failed. Attempt to acquire and collect any missing Java dumps manually. See the problem determination information on the WebSphere Application Server Support web page for information on how to manually generate javacores: http://www.ibm.com/software/webservers/appserv/was/support |
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 a 64-bit Java 8 version 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 specified value is not appropriate for the specified option. |
Action | Run the `server help` command for a description of the options. If the value is a number, ensure it is in the valid range. |
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 | The specified option is not allowed for the specified command. |
Action | Run the `server <command> help` command to get information about valid options for the command. |
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 8, or adjust the JAVA_HOME system variable to point to Java 8. |
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 system cannot write to the location. |
Action | Ensure that there is enough disk space to create the server and that the location has the correct write permissions before you try to create the server 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. |
Explanation | The specified thread called a method to exit the JVM. The server intercepted the request and will attempt to stop in an orderly manner. |
Action | If stopping the server was unexpected, determine why the specified thread called the method. |
Explanation | The server intercepted a request to stop the JVM and will attempt to stop in an orderly manner. The JVM might be exiting because the operating system sent a terminating signal to the server process. |
Action | If stopping the server was unexpected, determine if a terminating signal was sent to the server process. |
Explanation | The specified option must be followed by an equals sign (=) and a value. |
Action | The option must be specified in the following format: --option=value. |
Explanation | The server command port is required for communication with a running server. The command port was explicitly disabled for this server, therefore it is not possible to tell when the server has completed startup. |
Action | Manually check the server logs to verify that the server started successfully. |
Explanation | The server command port is required for communication with a running server. The command port was explicitly disabled for this server, therefore it is not possible to tell when the server has completed startup. |
Action | Manually check the server logs to verify that the server started successfully. |
Explanation | The server command port is required for communication with a running server. The command port is disabled for this server, therefore it cannot be stopped from this script. Note that the command port is disabled by default when a server is started as a started task on z/OS. |
Action | If the server is running as a started task on z/OS, the server can be stopped from the operator console. Otherwise, the server process can be stopped from a shell. |
Explanation | The server command port is required for communication with a running server. The command port is disabled for this server, therefore some portions of the server dump that require direct communication to the server could not be obtained. Note that the command port is disabled by default when a server is started as a started task on z/OS. |
Action | If the server is running as a started task on z/OS, a full server dump can be requested from the operator console. See the information center for details. |
Explanation | The server command port is required for communication with a running server. The command port is disabled for this server, therefore the requested dump could not be taken. Note that the command port is disabled by default when a server is started as a started task on z/OS. |
Action | If the server is running as a started task on z/OS, this dump can be requested from the operator console. See the information center for details. |
Explanation | This message is for informational purposes only. Please refer to the system log for details on the dataset name and volume that contains the output of the Java system dump. |
Action | No action is required. |
Explanation | The directory create operation did not succeed. The disk might be full or the server might not have permission to write to the location. |
Action | Verify the directory location and permissions to see if the problem can be resolved. |
Explanation | The server puts the package file that it creates into the path specified in the loose configuration application XML file. However, the path in the loose configuration application XML file has at least one unknown symbol in it. You can find known symbols in the WLP_HOME/README.TXT file. The location symbols are wrapped in ${...} text. |
Action | Change the path in the loose configuration application XML file to use known location symbols. |
Explanation | The specified loose configuration application XML file contains invalid information about the location of the files. For example, it might specify a directory that cannot be found. Paths in this XML file should be relative to the configuration directory of the server. The archive represented by this file will not be included in the packaged server output. |
Action | Modify the paths in the loose configuration application XML file to point to the correct location that contains the application files. |
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 | This product is licensed for development and limited production use. To see the definition of development use and understand the production limitations, read the product license files. |
Action | No action is required. |
Explanation | This product is licensed for development use. To see the definition of development use and understand the limitations, read the product license files. |
Action | No action is required. |
Explanation | The value for the specified configuration parameter is not, or cannot be converted to, a string or string array. |
Action | Check the value specified in the server configuration and ensure the value is a valid representation of a string or string array. |
Explanation | The process that is attempting to create the server was not able to determine the level of Java in use. This level is required in order to determine the optimal settings for the server. |
Action | Ensure that you are using a supported JDK. You might also need to modify your JAVA_HOME environment variable to point to a supported JDK installation. |
Explanation | The value for the specified configuration parameter is not, or cannot be converted to, a string or string collection. |
Action | Ensure that the value specified in the server configuration is a valid representation of a string or string collection. |
Explanation | The process that is attempting to create the server was not able to generate a server.env file in the specified location. This file provides the required JVM arguments for the server to function properly. |
Action | Ensure that you have write access to the server directory and that you have sufficient disk space. You must ensure that the server process has read access to this file. |
Explanation | The value for the specified configuration parameter is not, or cannot be converted to, a boolean value. |
Action | Ensure that the value specified in the server configuration is a valid representation of a boolean value. |
Explanation | This product is a beta and must be used according to the terms of the beta license. |
Action | No action is required. |
Explanation | The value for the specified configuration parameter is not, or cannot be converted to, a long value. |
Action | Ensure that the value specified in the server configuration is a valid representation of a long value. |
Explanation | The PID file for this server was not created within the wait period. The server's start status could not be verified. |
Action | Manually verify the status of the newly started server. |
Explanation | The value for the specified configuration parameter is not, or cannot be converted to, a integer value. |
Action | Ensure that the value specified in the server configuration is a valid representation of an integer value. |
Explanation | The STC procedure specified by the WLP_ZOS_PROCEDURE property in server.env failed to start. |
Action | Verify that the procedure name provided exists and is not surrounding by single or double quotes. Check the MCGRE return code for further details and actions. |
Explanation | The value for the specified configuration parameter is not, or cannot be converted to, an integer array. |
Action | Ensure that the value specified in the server configuration is a valid representation of an integer array. |
Explanation | The procedure name, server name, and start parameters provided to start the server as a started task exceeded the maximum MVS console command length. |
Action | Shorten the server name and procedure name so that the MVS start command will be less than 126 characters. |
Explanation | The value for the specified configuration parameter is not, or cannot be converted to, a duration value. |
Action | Ensure that the value specified in the server configuration is a valid representation of a duration value. |
Explanation | This message is for informational purposes only. The product extension was added by a call to the com.ibm.wsspi.kernel.embeddable.ServerBuilder.addProductExtension SPI. |
Action | No action is required. |
Explanation | The platform uses symbolic paths to provide rudimentary protection from arbitrary access to the file system when the location service is used to resolve specified paths. README.TXT contains information about how symbolic paths are configured. |
Action | Check bootstrap.properties for configured paths, and ensure that the configured path is a child of existing symbols or is associated with an explicitly defined symbol. |
Explanation | The path specified for a symbol exists, and is a different type of resource than the path specifies (for example, the symbol describes a file, but the resource is a directory). |
Action | Ensure the path is specified correctly. Directory paths must end with a /. Ensure the path refers to a resource that either does not exist, or exists and is of the required type. |
Explanation | The directory specified as the java.io.tmpdir (either through a system property or a platform-specific environment variable) does not exist and could not be created. |
Action | Ensure the specified directory exists and has read/write permissions. |
Explanation | The directory specified as the java.io.tmpdir (either through a system property or a platform-specific environment variable) was relative, and is resolved relative to the launch directory. |
Action | No action is required. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The framework is shutting down because of a previous error during initialization. |
Action | Resolve the error then restart the server. |
Explanation | The value for the specified configuration parameter was not, or could not be converted to, a String value. |
Action | Check the value specified in the server configuration. |
Explanation | The value for the specified configuration parameter could not be parsed as a monitor interval. |
Action | Check the value specified in the server configuration and ensure the value is a valid monitor interval. For example, 1s for one second. Valid units are ms=milliseconds, s=seconds, m=minutes, h=hours. |
Explanation | The service could not create a cache location for a set of monitored resources. |
Action | Verify that you have write access to the server directory and workarea. |
Explanation | An unexpected exception occurred while creating a monitor for the specified resource. The resource will not be monitored. |
Action | Verify that you have read access to the specified resource. See the exception and the associated FFDC message for more information. |
Explanation | The service could not delete a cache location for a set of monitored resources. |
Action | Verify that you have write access to the server directory and workarea |
Explanation | An unexpected exception occurred while creating a monitor for the specified resource. |
Action | See the exception and the associated FFDC message for more information. |
Explanation | Too many consecutive exceptions occurred while notifying a monitor for the specified resource. The resource will no longer be monitored. |
Action | See the exceptions and the associated FFDC messages for more information. |
Explanation | There is no support of inputting arguments from the current console. |
Action | Switch to other standard consoles that accepts input arguments. |
Explanation | Unable to read the input from the console. |
Action | Investigate the root cause of the exception. |
Explanation | The task is not supported by the current command. |
Action | Use help command to show all the available tasks. |
Explanation | Unable to find the server version file. |
Action | Verify that the server is fully installed. |
Explanation | Unable to read the target file. |
Action | Investigate the root cause of the exception. |
Explanation | Unable to write the target file. |
Action | Investigate the root cause of the exception. |
Explanation | Unable to initialize the target task. |
Action | Investigate the root cause of the exception. |
Explanation | Unable to find the specified product checksum file . |
Action | Verify that the checksum file exists. |
Explanation | Unable to load the specified checksum file. |
Action | Verify that the checksum file is a well-formed file with file path string and MD5 string pair. |
Explanation | A malformed Unicode escape appears. |
Action | Investigate the root cause of the exception. |
Explanation | Cannot find any properties files in the lib/versions folder of the Liberty profile installation directory. |
Action | Use validate command to verify whether the current Liberty profile installation is valid. |
Explanation | Cannot find the version properties directory lib/versions folder under the Liberty profile installation directory. |
Action | Use validate command to verify whether the current Liberty profile installation is valid. |
Explanation | The lib/versions of the Liberty profile installation directory is not a directory. |
Action | Use validate command to verify whether the current Liberty profile installation is valid. |
Explanation | Unable to read the target file. |
Action | Investigate the root cause of the file can not be read. |
Explanation | The option supplied on the command line is not supported by this command. |
Action | Reissue the command without the invalid option or with a valid option. |
Explanation | The tool requires a Java SDK, but it was launched using a plain Java runtime environment. |
Action | Set the JAVA_HOME environment variable to the path of a Java SDK, and then try the command again. |
Explanation | The tool requires a Java compiler. However, the tool was launched without one. |
Action | Verify that the java.compiler module is available in your Java image. Then, verify that it is available at run time by specifying the following command-line option: --add-modules java.compiler |
Explanation | A user issued a command that is processed by the infrastructure for pausing components. However, the command could not be processed. The server might be initializing or shutting down. |
Action | Verify that the server has fully initialized and is not in the process of shutting down. |
Explanation | A warning message was logged using the OSGi log service. |
Action | See the warning message for information. |
Explanation | An error message was logged using the OSGi log service. |
Action | See the error message for information. |
Explanation | A BundleException was thrown by the OSGi Framework. |
Action | See the exception message for information. |
Explanation | An informational message was logged using the OSGi log service. |
Action | No action is required. |
Explanation | An audit message was logged using the OSGi log service. |
Action | No action is required. |
Explanation | The JNDI feature provides a JNDI registry and associated utilities. This is normally required if an application or feature needs to look up entries in a JNDI context. |
Action | Ensure that a JNDI implementation is provided (e.g. by configuring the JNDI feature in the configuration for this server). |
Explanation | A character that is not valid has been used in the client name. |
Action | Rename the client using only valid characters: Unicode alphanumeric (e.g. 0-9, a-z, A-Z), underscore (_), dash (-), plus (+), and period (.). |
Explanation | You may specify only one client on the command line. The first client name has been processed; the remaining names have been ignored. |
Action | No action is required. Specify only one client to avoid this warning. |
Explanation | The specified client could not be created. |
Action | Check and resolve the exception, then try again to create the client. |
Explanation | The specified client does not exist, so no action can be performed on it. |
Action | Check the name of the client, or create a client with the specified name, then retry the command. |
Explanation | The client directory must not already exist when creating a client. |
Action | Either choose a new client name or delete the directory, then rerun the command. |
Explanation | The specified client cannot be created because another application was performing file operations in the new client directory. |
Action | Investigate why there was file activity in the client directory outside the create command then delete the client directory and try to create the client again. |
Explanation | The specified client cannot be created either because there was not enough space to create the client or because the location is prevented from being written to. |
Action | Ensure that there is enough disk space to create the client 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 | 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 | This message is for informational purposes only. |
Action | No action is required. |
Explanation | Java 2 Security is enabled but a failure occurred setting the default Security Manager. |
Action | Ensure that the security manager has not already been set by starting the server with the -Djava.security.manager option. If already set, remove the -Djava.security.manager option, and restart the server with Java 2 Security enabled by specifying the websphere.java.security property in the bootstrap.properties file. |
Explanation | Java 2 Security is enabled but a failure occurred setting the NoRethrow Security Manager. |
Action | Ensure that the security manager has not already been set by starting the server with the -Djava.security.manager option. If already set, remove the -Djava.security.manager option, and restart the server with Java 2 Security enabled by specifying the websphere.java.security property in the bootstrap.properties file. |
Explanation | The Java Security Manager checkPermission() threw a SecurityException on the subject Permission. |
Action | Verify that the attempted operation is permitted and update the permissions policy file for the bundle or application as needed. |
Explanation | A failure occurred determining the code base location of the code which has generated a Java 2 Security Permission access control exception. |
Action | Check the exception and server logs for details. Ensure that the security manager has not already been set by starting the server with the -Djava.security.manager option and specifying a -Djava.security.policy option. If either or both are set, remove the settings and restart the server with Java 2 Security enabled by specifying the websphere.java.security property in the bootstrap.properties file. |
Explanation | The Java Security Manager checkPermission() threw a SecurityException on the subject Permission. A caller on the call stack does not have the required permission. This might not be a problem if the caller properly handles this exception. |
Action | Verify that the attempted operation is permitted by examining all Java 2 security policy files and application code. Additional permissions might be required, an AccessController.doPrivileged call might be needed in some code on the call stack, or the Security Manager has properly prevented access to a resource that a caller does not have permission to access. |
Explanation | The Java Security Manager checkPermission() threw a SecurityException. A caller on the call stack does not have the required permission. |
Action | Verify that the attempted operation is permitted by examining all Java 2 security files and application code. Additional permissions might be required. |
Explanation | A client feature was not enabled, or an error occurred while loading the feature. |
Action | Ensure that a client feature is enabled, and check for error messages. |
Explanation | The product received an error from the running client application. |
Action | See error messages for details about the client application error. |
Explanation | An error occurred while attempting to perform the requested operation. |
Action | Check the server logs for details about the operation error. |
Explanation | The Java Security Manager checkPermission() threw a SecurityException due to the class not having the required permissions. |
Action | Verify that the attempted operation is permitted and update the permissions policy file for the bundle or application as needed. |
Explanation | The Java Security Manager checkPermission() threw a SecurityException for a class at the specified code base location. |
Action | Verify that the attempted operation is permitted and update the permissions policy file for the bundle or application as needed. |
Explanation | The Java Security Manager checkPermission() threw a SecurityException on the subject Permission. |
Action | Verify that the attempted operation is permitted and update the permissions policy file for the bundle or application as needed. |
Explanation | The lib/extract directory contains metadata and self extraction classes required for the package command to complete. If this directory is missing, it could indicate that the installation of WebSphere Liberty Profile was incomplete or that the directory was deleted. |
Action | Reinstall WebSphere Liberty Profile and ensure that the lib/extract directory exists under the WLP_HOME directory. |
Explanation | A user issued a request to pause all pause capable components in the server. The server will attempt to pause these components. |
Action | No action is required. |
Explanation | A user issued a request to pause specific components in the server. The server will attempt to pause these components. |
Action | No action is required. |
Explanation | A user issued a request to resume all paused components in the server. The server will attempt to resume these components. |
Action | No action is required. |
Explanation | A user issued a request to resume specific components in the server. The server will attempt to resume these components if paused. |
Action | No action is required. |
Explanation | A user issued a pause request. However, the request could not be processed. The server might still be initializing or shutting down. |
Action | Verify that the server has fully initialized and is not in the process of shutting down. |
Explanation | A user issued a resume request, but the request could not be processed. The server might still be initializing or shutting down. |
Action | Verify that the server is fully initialized and is not in the process of shutting down. |
Explanation | The server processed a pause request, but some pause capable components failed to pause. All other pause capable components paused successfully. |
Action | Check the server logs for additional errors from the failed components. |
Explanation | The server processed a resume request, but some paused components failed to resume. All other paused components resumed successfully. |
Action | Check the server logs for additional errors from the failed components. |
Explanation | A user issued a pause request with an empty target list on the target option. The request completed but no action was taken. |
Action | Specify on the target option a list of components to pause. To pause all pause capable components in the server, issue a pause request without the target option. |
Explanation | A user issued a resume request with an empty target list on the target option. The request completed but no action was taken. |
Action | Specify on the target option a list of components to resume. To resume all paused components in the server, issue a resume request without the target option. |
Explanation | The server processed a pause request, but no pause capable components were found on the server. No action was taken. |
Action | Verify that pause capable components are available in the server. |
Explanation | The server processed a resume request, but no pause capable components were found. No action was taken. |
Action | Verify that pause capable components are available in the server. |
Explanation | The server processed a pause request, but some specific components could not be found. The request was processed for all other components specified. |
Action | Verify that the specified component names are correct and that the components are registered in the server and pause capable. |
Explanation | The server processed a resume request, but some specific components were not found. The request was processed for all other components specified. |
Action | Verify that the specified component names are correct and that the components are registered in the server and pause capable. |
Explanation | The server processed a status request, but some specific components were not found. The request was processed for all other components specified. |
Action | Verify that the specified component names are correct and that the components are registered in the server and pause capable. |
Explanation | A pause request completed. |
Action | No action is required. |
Explanation | A resume request completed. |
Action | No action is required. |
Explanation | The WLP_PRODUCT_EXT_DIR environment variable points to the location of the product extension. The server found and is using the product extension. |
Action | No action is required. |
Explanation | Only alphanumeric characters are allowed in variable names specified in the server.env file. |
Action | Either modify the variable name to only use alphanumeric characters or move the definition of the variable to the bootstrap.properties file. |
Explanation | The STC procedure name specified by the WLP_ZOS_PROCEDURE property in the server.env file is not valid. The procedure name must be no longer than 8 characters and must not contain a comma. |
Action | Verify that the procedure name is no longer than eight characters and that it does not contain a comma. |
Explanation | The STC job name specified by the WLP_ZOS_JOBNAME property in the server.env file is not valid. The job name must be no longer than 8 characters and must not contain a comma. |
Action | Verify that the job name is no longer than eight characters and that it does not contain a comma. |
Explanation | The server command port is required for communication with a running server. The command port is disabled for this server, therefore the pause request could not be processed. Note that the command port is disabled by default when a server is started as a started task on z/OS. |
Action | Enable the command port for this server. If the server is running as a started task on z/OS, this pause can alternatively be requested from the operator console. |
Explanation | The server command port is required for communication with a running server. The command port is disabled for this server, therefore the resume request could not be processed. Note that the command port is disabled by default when a server is started as a started task on z/OS. |
Action | Enable the command port for this server. If the server is running as a started task on z/OS, this resume can alternatively be requested from the operator console. |
Explanation | A user issued a status request with an empty target list on the target option. The request completed but no action was taken. |
Action | Specify on the target option a list of components to check their status. To check the cumulative status of all pause capable components in the server, issue status request without the target option. |
Explanation | Some operating system memory information was not in the expected format. The product could be reading a file or running a program when it encounters the unexpected format. The message text provides either the name of an operating system file and the contents of the file or the name of a program and the output of the program. You can use this information to troubleshoot the problem. |
Action | Review the information in the message text. Correct any issues to ensure that the operating system is behaving correctly and that no unexpected operating system memory information is encountered. |
Explanation | The user performed a package request with a --server-root option specifying an empty argument and Product Extensions were detected. The default server root of wlp will be used. |
Action | No action is required. |
Explanation | This function has not been implemented for this operating system. |
Action | Use the OperatingSystem API to get the type of operating system and avoid calling this function for this type of operating system. |
Explanation | The user performed a package request with a --server-root option and --include=runnable, which is not an allowed combination. The default server root of wlp is used. |
Action | No action is required. |
Explanation | This function has not been implemented for this operating system. |
Action | Use the OperatingSystem API to get the type of operating system and avoid calling this function for this type of operating system. |
Explanation | A variety of situations can cause the failure. For example, the program failed due to an error condition that it reports in the return code and output. |
Action | Ensure that the command exists and that it is in one of the directories in the PATH environment variable. |
Explanation | The --archive option must include a file extension that ends with .jar when specifying --include=runnable. |
Action | Supply a file name to --archive with a file extension of .jar when specifying --include=runnable. |
Explanation | The --archive option must not end with a .jar file extension when --include=usr is specified. |
Action | Supply a file name to --archive with a file extension other than a .jar file extension when --include=usr is specified. |
Explanation | The directory that contains version information files either does not exist or cannot be read by the current user. |
Action | Ensure that the directory exists and can be read by the current user. |
Explanation | New features that are not fully tested are made available in early releases to elicit feedback before they are included in a supported release. |
Action | Do not use an early release version on production systems, since early release versions are not supported. |
Explanation | An unknown phase was specified as the value of the checkpoint option. |
Action | Review the documentation to determine valid phase names. Reissue the command using a valid checkpoint phase. |
Explanation | As part of the deprecation of the Java Security Manager, as specified by JEP 411, Liberty does not support the Java Security Manager with Java 18 or later. |
Action | Remove the websphere.java.security property from the bootstrap.properties file or use a Java version that is earlier than Java 18. |
Explanation | Java Security Manager could not be enabled because the system is using Java 18, which by default disallows use of a Java Security Manager. |
Action | Start the server with the JVM argument -Djava.security.manager=allow. |
Explanation | An error occurred restoring the checkpoint workarea directory. |
Action | Ensure that the user has sufficient permissions to restore the checkpoint workarea. Reissue the command with a user that has sufficient permissions. |
Explanation | Liberty does not support the Java Security Manager when a server checkpoint is requested. The Java Security Manager is deprecated, as specified by JEP 411. |
Action | Remove the websphere.java.security property from the bootstrap.properties file. |
Explanation | A checkpoint request for the server failed because an existing checkpoint image cannot be deleted. |
Action | Ensure the user has permission to delete the existing directory. Reissue the command with a user that has sufficient permissions. |
Explanation | An error occurred backing up the checkpoint server workarea directory. |
Action | Ensure that the user has sufficient permissions to back up the checkpoint workarea directory. Reissue the command with a user that has sufficient permissions. |
Explanation | An error occurred restoring a checkpoint server process. The server launched without using the checkpoint image. |
Action | Check the logs to determine why the checkpoint process was not restored. |
Explanation | A checkpoint request for the server failed. No valid checkpoint process image for the server was created. |
Action | To determine why the checkpoint failed, inspect the log files in the checkpoint directory that is located in the server logs directory. |
Explanation | A checkpoint request for the server failed because netlink system calls were unsuccessful. |
Action | If SELinux is enabled in enforcing mode, netlink system calls might be blocked by the SELinux "virt_sandbox_use_netlink" policy setting. Either disable SELinux or enable the netlink system calls with the "setsebool virt_sandbox_use_netlink 1" command. |
Explanation | An error occurred restoring a checkpoint server process. The server did not launch because checkpoint restore recovery is disabled. |
Action | Check the logs to determine why the checkpoint process was not restored. To enable restore failure recovery, set the CRIU_RESTORE_DISABLE_RECOVERY environment variable to true. |
Explanation | The server waits for up to 30 seconds for services to quiesce before proceeding with shutdown. |
Action | No action is required. |
Explanation | The quiesce operation completed successfully. |
Action | No action is required. |
Explanation | The process was unable to quiesce all services within 30 seconds. |
Action | You can safely ignore error messages that are the result of unavailable required services. |
Explanation | The client waits for up to 30 seconds for services to quiesce before proceeding with shutdown. |
Action | No action is required. |
Explanation | The quiesce operation completed successfully. |
Action | No action is required. |
Explanation | One or more updates to features, configuration, or applications did not complete before the server shutdown. |
Action | No action is required. |
Explanation | One or more operations that were initiated during the shutdown operation did not complete. |
Action | No action is required. |
Explanation | One or more threads that were active before shutting down the server were still active at the end of the quiesce period. |
Action | No action is required. |
Explanation | An error occurred which caused an executor to hang and the Liberty run time added a significant number of threads in an attempt to end the hang condition. However, the executor remains in an unresponsive state. |
Action | Determine if there is a bottleneck, such as a locked database table, that might prevent threads from resolving in the server. If no such bottleneck exists and the server legitimately requires additional threads, adjust the coreThreads attribute of the executor configuration element. |
Explanation | The maxQueueSize attribute controls how many task submissions can queue up. The maxWaitForEnqueue attribute controls how long to wait for a queue position to become available, but this interval can be shortened by the remaining timeout if you use the timed invokeAll or invokeAny methods to submit tasks. The queueFullAction attribute determines what action to take after the interval elapses and no queue position becomes available. To avoid exceeding maximum concurrency or to honor the specified timeout, the invokeAll and invokeAny methods can override the queueFullAction and abort the task submission when it cannot be queued. |
Action | No action is necessary if the application handles RejectedExecutionException. Otherwise, take any combination of the following actions: increase maxQueueSize, increase maxWaitForEnqueue, use a different queueFullAction, or increase the timeout that is supplied to invokeAll or invokeAny methods. |
Explanation | Task submissions are not permitted after the executor service has been requested to shut down. |
Action | Only submit tasks on an executor service instance which has not been requested to shut down. |
Explanation | It is not possible to update configuration after the executor service has been requested to shut down. |
Action | Only update configuration of an executor service instance which has not been requested to shut down. |
Explanation | The executor rejected the invokeAll or invokeAny operation because there was insufficient time or queue capacity available to submit all of the tasks requested within the specified interval. |
Action | No action is necessary if the application handles the RejectedExecutionException. Otherwise, take any combination of the following actions: increase maxQueueSize, increase maxConcurrency, or increase the timeout value that is supplied to the invokeAll or invokeAny methods. |
Explanation | When a startTimeout is configured on an executor or programmatically requested for a task, the executor tracks the time elapsed between when the task is submitted and when it is possible to run the task. If the elapsed time exceeds the startTimeout, the executor aborts the task instead of starting it. |
Action | No action is necessary if the application expects some tasks to abort due to exceeding their startTimeout. Otherwise, take any combination of the following actions: increase startTimeout, increase maxConcurrency. |