Explanation | An exception occurred while processing the compressed data for the archive. |
Action | Check that the file is a valid archive. |
Explanation | The application structure appears to have changed, requiring deletion of cache data based on the previous structure. |
Action | If your application has changed structure, this is expected. |
Explanation | An error occurred during creation of cache data for the application, preventing the application from being processed correctly. |
Action | Check the reported cause. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | See the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | See the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | See the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | See the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | See the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | See the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | See the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | See the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | See the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | See the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | See the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | See the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | See the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | See the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | See the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | See the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | See the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | See the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | See the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | See the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | See the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | See the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | See the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | See the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | See the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | See the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | See the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | See the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | See the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | See the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | See the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | 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 XML file could not be found. |
Action | Ensure that the file is in the correct location and has not been moved. |
Explanation | The specified XML file could not be read. |
Action | Ensure that the file is correctly formatted as XML. |
Explanation | The XML file element has an "excludes" attribute that is not valid. The attribute was ignored. |
Action | Remove the "excludes" attribute from the element. |
Explanation | The XML archive element has an "excludes" attribute that is not valid. The attribute was ignored. |
Action | Remove the "excludes" attribute from the element. |
Explanation | The "excludes" attribute is not valid and cannot be understood. |
Action | Change the attribute to be the correct syntax or remove it if it is not needed. |
Explanation | The file declared for the workspace application could not be found. |
Action | Ensure that the file is in the referenced location, or that the referenced location matches the location of the file. |
Explanation | Shows the value of the variable. |
Action | No action is required. |
Explanation | A command was issued but ended with an unexpected return code. |
Action | Check command execute failure log. |
Explanation | The ant task attribute installDir must be set to a value other than null. |
Action | Define the installDir attribute value to a non-null value. |
Explanation | Server installation directory must contain lib/ws-launch.jar. |
Action | Please check that the server is installed correctly. Make sure lib/ws-lauch.jar exists. |
Explanation | The deploy task has be used; but no information on the file or fileset to be deployed has been specified. |
Action | Either add the file attribute or provide a nested fileset element. |
Explanation | The application is being deployed. |
Action | No action is required. |
Explanation | The Liberty server only supports deployment of war, eba, zip, ear and jar files. |
Action | Correct the application file name. |
Explanation | An attempt was made to start the application, but the Start application message is not found in console.log. |
Action | Check the server configuration files and investigate the cause of the failure to start the application. |
Explanation | An attempt was made to start the server, but the Server start message is not found in console.log. |
Action | Check console and trace log files to investigate the server start problems |
Explanation | A request was made to wait for a log file to contain the given text. |
Action | No action is required. |
Explanation | A request was made to wait for a log file to contain the given text, but the log file did not contain message before the search timed out |
Action | Investigate the cause of the missing message. |
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 | Search file does not exist. |
Action | Make sure search file exist. |
Explanation | A search has been requested for the given string in the given file. |
Action | No action is required. |
Explanation | A search has been requested for a string which has now been located. |
Action | No action is required. |
Explanation | A required attribute is missing on an ant task. |
Action | Define missing attribute. |
Explanation | A request was made to operate on a server that does not exist. The missing server will be created. |
Action | No action is required. |
Explanation | The package task has been used but the archive attribute specifies a directory rather than the name of a zip file. |
Action | Correct the value of the archive attribute. |
Explanation | The undeploy task requires the fileName attribute to be provided. |
Action | Specify the value of the fileName attribute. |
Explanation | The undeploy task cannot undeploy the application as the application does not exist. |
Action | Correct the value of the fileName attribute. |
Explanation | The undeploy task is deleting the application. |
Action | No action is required. |
Explanation | An attempt was made to undeploy the application, but the application stop message was not issued. |
Action | Check the console and trace log files to investigate the cause of the failure to stop the application. |
Explanation | The user name or password entered is incorrect. |
Action | Specify a valid user name and password. |
Explanation | The token type specified by the client application is not supported. Only LTPA tokens are supported. |
Action | Specify an LTPA token, because only LTPA tokens are supported. |
Explanation | The configuration administrative service is unavailable. |
Action | Verify if the configuration service is running. |
Explanation | The security service is unavailable. |
Action | Verify if the security service is running. |
Explanation | A user registry must be configured for this server. |
Action | Configure at least one user registry (e.g., LDAP, BasicUserRegistry, or QuickStartSecurity) for the server. |
Explanation | An exception occurred while accessing the user registry. |
Action | Check whether the user registry is configured correctly. |
Explanation | The defined configuration administrative object cannot be found. |
Action | There could be an error in the property definition. Ensure whether the property definitions in the server configuration file are correct. |
Explanation | There was an IOException while reading data from the server.xml file. |
Action | Validate the configurations specified in the server.xml file. |
Explanation | The user does not have the permission to access Liberty messaging service. |
Action | Specify a valid user name that is authenticated to connect to the Liberty messaging service. |
Explanation | The specified user is not authorized to perform the designated action on indicated destination. |
Action | Specify a user that is authorized to perform the specified action on the indicated destination. |
Explanation | The user is not authorized to connect to the Liberty messaging services. |
Action | Specify a user that is authorized to connect to the Liberty messaging service. |
Explanation | A name is not allowed to be used for multiple roles. |
Action | Provide a different name to avoid duplicate entries for a role. |
Explanation | The user is not authorized to perform the specified action on the indicated destination. |
Action | Provide a user that is authorized to perform the specified action on the indicated destination. |
Explanation | The MQTT server is initializing. |
Action | No action is required. |
Explanation | The MQTT server started successfully. |
Action | No action is required. |
Explanation | The MQTT server is shutting down. |
Action | No action is required. |
Explanation | The MQTT server stopped successfully. |
Action | No action is required. |
Explanation | An unexpected error occurred during MQTT server initialization. |
Action | Check the logs to determine the problem that causes the error, correct the problem, and then restart the server. |
Explanation | An unexpected error occurred when the MQTT server was shutting down. |
Action | Check the logs to determine the problem that causes the error and correct the error. |
Explanation | Last Will and Testament message could not be sent. |
Action | Check the logs to determine the cause of the error. |
Explanation | The PINGREQ message has not arrived within the Keep Alive time specified. Hence the client is disconnected. |
Action | Check for any network problems or ensure that the client is not disconnected without issuing the DISCONNECT packet. |
Explanation | Unique name is required for the element in each web-fragment.xml file while when using relative sorting ordering. |
Action | Assign unique name for each web-fragment.xml while when using relative sorting ordering or Configure Use absolute sorting <absolute-ordering> element in the web.xml file. |
Explanation | The manifest class path can not be found in the jar file or in the archive that enclose the jar file. |
Action | Add the class path target to the archive. |
Explanation | The class path is not specified correctly. It must be a relative URI string that points to a jar file or a folder. |
Action | Update the jar file's MANIFEST.MF to provide correct Class-Path definition. |