| 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 | An error occurred during creation of cache data for the application, preventing the application from being processed correctly. |
| Action | Check that the nested archive is a valid archive. |
| Explanation | A concurrent request to extract a nested archive timed out waiting for the initial extraction to complete. |
| Action | Check that the nested archive is a valid archive. |
| Explanation | A concurrent request to extract a nested archive completed but did not extract the nested archive. |
| Action | Check that the nested archive is a valid archive. |
| Explanation | A concurrent request to extract a nested archive completed but did not produce a simple file. |
| Action | Check that the nested archive is a valid archive. |
| Explanation | A concurrent request to extract a nested archive completed but produced a different file than was expected. |
| Action | Check that the nested archive is a valid archive. |
| Explanation | An extraction of a nested archive has detected a directory as the prior extracted archive. |
| Action | Clean then restart the server to ensure no prior cache contents are present. |
| Explanation | An extraction of a nested archive has detected an untypable file as the prior extracted archive. |
| Action | Clean then restart the server to ensure no prior cache contents are present. |
| Explanation | A request to open an archive file failed because the archive file cache is not active. |
| Action | This message indicates an internal programming error. |
| Explanation | Archive file close processing was requested for an archive file which was not opened. |
| Action | This messages indicates an internal programming error. |
| Explanation | Archive file close processing was requested for an archive file which was already closed. |
| Action | This messages indicates an internal programming error. |
| Explanation | An unexpected update was made to an application archive file while that archive was open. This usually occurs because a dynamic update was made to application files. |
| Action | Restart the server. When updating application files, wait for the server to quiesce, plus wait at least a half second to allow application files to be closed. |
| Explanation | An unexpected update was made to an application archive file while that archive was open. This usually occurs because a dynamic update was made to application files. |
| Action | Restart the server. When updating application files, wait for the server to quiesce, plus wait at least a half second to allow application files to be closed. |
| Explanation | An unexpected change has caused an open application archive file to be re-opened. The server has attempted to obtain the updated contents of the archive file, but may not have fully updated internal listings of the archive contents. |
| Action | Restart the server. When updating application files, wait for the server to quiesce, plus wait at least a half second to allow application files to be closed. |
| Explanation | An exception occurred during archive processing because the specified file was not found. |
| Action | Check that the specified file exits and has permissions that are readable by the server. |
| Explanation | The archive that is used in the resource URL has entries that are contained within the directory, but the archive is missing an entry for the directory itself. The directory URL is not returned. This omission can cause some applications that scan for resources to fail to find some resources in the archive file. |
| Action | The archive file must be built to include all the directory entries. |
| Explanation | Archive file close processing was requested for an archive file which is already pending closure. |
| Action | This messages indicates an internal programming error. |
| Explanation | The Liberty file system is not consistent with the overlay configuration. This can occur because the server was restarted with changes to the overlay configuration. |
| Action | Restart the server with the '--clean' option. |
| Explanation | The Liberty file system is not consistent with the overlay configuration. This can occur because the server was restarted with changes to the overlay configuration. |
| Action | Restart the server with the '--clean' option. |
| Explanation | The Liberty file system is not consistent with the overlay configuration. This can occur because the server was restarted with changes to the overlay configuration. |
| Action | Restart the server with the '--clean' option. |
| Explanation | The Liberty file system is not consistent with the overlay configuration. This can occur because the server was restarted with changes to the overlay configuration. |
| Action | Restart the server with the '--clean' option. |
| Explanation | The Liberty file system is not consistent with the overlay configuration. This can occur because the server was restarted with changes to the overlay configuration. |
| Action | Restart the server with the '--clean' option. |
| Explanation | The Liberty file system is not consistent with the overlay configuration. This can occur because the server was restarted with changes to the overlay configuration. |
| Action | Restart the server with the '--clean' option. |
| 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 application contains a Java EE annotation with the 'javax' package name, but the application server has Jakarta EE features enabled. The application server did not process the 'javax' package name annotation. |
| Action | Modify the application to use the 'jakarta' package name version of the annotation or modify the application server configuration to enable Java EE features. |
| 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 | 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. |