Explanation | A key was passed into the Messages class to resolve to a string, but a properties file for the locale could not be found and the appropriate message could not be retrieved. |
Action | Determine why the message catalog could not be found. |
Explanation | The transaction setting for the start and stop methods on a startup bean must not be marked as TX_MANDATORY. |
Action | Mark the stop and start methods with any transaction setting other than TX_MANDATORY. |
Explanation | An unexpected exception occurred looking up the home for the startup bean. |
Action | Verify the EAR deploy worked correctly and that the beans were deployed. |
Explanation | An unexpected exception occurred creating an instance of the startup bean. |
Action | Verify the EAR containing the startup bean deployed correctly. |
Explanation | The specified startup bean start method returned "false" causing the application start up to be aborted. |
Action | Determine why the startup bean returned "false" and correct the problem allowing the application to start. |
Explanation | An unexpected exception occurred calling the start or stop method of the startup bean. |
Action | Verify why the method throws an exception. |
Explanation | The startup service failed to initialize. |
Action | Verify the application server installation. |
Explanation | The Startup Beans service has been disabled in the configuration, and will not process any Startup Beans. |
Action | Disabling this service may cause other services on the server to fail. If you wish to enable the service, use the Administrative Console to configure services on this application server. |
Explanation | The Startup Beans service has been disabled in the configuration but will continue to run because because of service dependencies. |
Action | Enable the Startup Beans service in the configuration to avoid receiving this message in the future. |
Explanation | The Startup Beans service experienced an error during initialization. The service will be inaccessible on the given server. The root error should have been logged previously. |
Action | Try to resolve the previously logged errors. If unable to do so, contact IBM product support. |
Explanation | The Startup Beans service was started and is ready to process all Startup Beans. |
Action | No user action required. |
Explanation | The Startup Beans service is stopping and will be unable to process any Startup Beans. |
Action | No user action required. |
Explanation | The Startup Beans service has stopped and will be unable to process any Startup Beans. |
Action | No user action required. |
Explanation | The Startup Beans service could not resolve the specified service, which is required for the Startup Beans service. Look through the log to determine the specified service started successfully. |
Action | If you wish to use the Startup Beans service, correct the problem with the specified service. If you are unable to correct the problem, please contact IBM product support. |
Explanation | The Startup Beans service has successfuly initialized. |
Action | No user action required. |
Explanation | The wasStartupPriority environment reference value for the specified startup bean is not an Integer. |
Action | Change the wasStartupPriority value for the specified EJB to a java.lang.Integer. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | 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/. |