Explanation | The server has started the application successfully. |
Action | No action is required. |
Explanation | The server could not start the application. |
Action | Read the exception message for information. |
Explanation | The server has updated the application successfully. |
Action | No action is required. |
Explanation | The server could not update the application. |
Action | Read the exception message for further information. |
Explanation | The server is not currently configured with all the required features for applications of this type, and so the application could not be started. |
Action | Modify the server configuration to include all the features that are required to support this type of application. |
Explanation | When trying to download an application to install, the server could not create the download directory. |
Action | Ensure that there is enough disk space for the download. |
Explanation | The server could not download the application. |
Action | If you intended the server to download the application, check that the file is available for download. |
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 server has stopped the application successfully. |
Action | No action is required. |
Explanation | The server could not stop the application. |
Action | Ensure that the application is in a state where it can be stopped. |
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 application could not be started because of earlier errors. |
Action | Check the application configuration and check the logs for errors during the application start. |
Explanation | The application name must be unique. This might be because two applications have been configured to have the same name, or a single application has been deployed both by configuration in the server.xml file and by putting the application in the dropins directory. |
Action | If two applications have the same name, remove or rename one of the applications. If a single application has been deployed in two different ways, change the configuration so that only one deployment method is used. |
Explanation | When trying to start the application, the server could not find the application at the specified location (or relative locations if it was a relative path). |
Action | Check that the location defined is correct for the application. |
Explanation | An application has been configured without specifying a location or a name. |
Action | Update the configuration to add a location. |
Explanation | An application has been configured without specifying a location. |
Action | Update the configuration to add a location. |
Explanation | An application was configured without specifying a type. The type could not be determined from the location. |
Action | Update the configuration to add a type. |
Explanation | The application is being started. |
Action | No action is required. |
Explanation | The whole application could not start. This might happen with an ear containing two wars where only one war will start. |
Action | Resolve the problem with the part of the application that could not start and redeploy the application. |
Explanation | The application could not be started because of earlier errors. |
Action | Check the application configuration and check the logs for errors during the application start. |
Explanation | The archive, or directory at the specified location is not valid so the application cannot start. |
Action | Ensure the identified archive or directory is valid. |
Explanation | The application did not start in the expected time. This could be because the server is overloaded or the application is large. If the application is starting as part of server startup, the server startup will finish without waiting for the application to start. |
Action | If the application takes a long time to start then no action is required; otherwise check the server logs to see if other messages indicate a cause. |
Explanation | The application monitor could not find the application running on the server. |
Action | No action is required. |
Explanation | The application monitoring service uses the file name, without the extension, to generate the application name. The application monitoring service could not determine an application name after the extension was removed from the file name. |
Action | Ensure that the file name for the application does not start with a period (.) and has a name before the file extension. |
Explanation | The application monitoring service could not determine the type of the application from either its file extension or parent directory. |
Action | Ensure that the file for the application either has an file extension that identifies the application type, or is under a directory whose name identifies the application type. |
Explanation | The application monitor could not start the application. |
Action | No action is required. |
Explanation | The application monitor could not read the list of all started applications. |
Action | Start the server with a cold start. |
Explanation | The server is monitoring a directory for applications to be deployed. |
Action | No action is required. |
Explanation | An application that is currently configured in the server.xml file has been deleted. |
Action | If the deletion was intentional, remove the application configuration from the server.xml file. |
Explanation | The old directory could not be removed even though it is no longer in use. |
Action | If the old directory is no longer needed, remove it. If it is still needed no action is required. |
Explanation | An application was installed but monitoring was not started on it so if a file is updated within the application the change will not be detected by the server. |
Action | When updating files in this application the application will need to be uninstalled and re-installed into the server. |
Explanation | An application element in the server configuration has defined the location of the application to be inside the directory that is monitored for applications. As a result the application element will be ignored, and the application will be started using the contents of the monitored directory if the application is present in that the monitored directory. |
Action | Either correct the application element or change the location of the monitored directory. |