ERR_MISSING_KEY=STUP0001E: Message key {0} was not found in any searched resource bundles. 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. Determine why the message catalog could not be found. ERR_INVOKE=STUP0006E: Exception calling startup bean named {0}, exception was {1} An unexpected exception occurred calling the start or stop method of the startup bean. Verify why the method throws an exception. STARTUPSVC_CANNOT_BE_DISABLED=STUP0009I: The Startup Beans service cannot be disabled. The Startup Beans service has been disabled in the configuration but will continue to run because because of service dependencies. Enable the Startup Beans service in the configuration to avoid receiving this message in the future. INVALID_PRIORITYTYPE=STUP0016W: Startup Bean {0} has a wasStartupPriority value with an incorrect type. The wasStartupPriority environment reference value for the specified startup bean is not an Integer. Change the wasStartupPriority value for the specified EJB to a java.lang.Integer. ERR_NO_SERVICE=STUP0014E: The Startup Beans service could not resolve the {0} service. 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. If you wish to use the Startup Beans service, correct the problem with the specified service. Contact IBM product support if you are unable to correct the problem. STARTUPSVC_NOT_ENABLED=STUP0008I: The Startup Beans service is disabled. The Startup Beans service has been disabled in the configuration, and will not process any Startup Beans. 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. STARTUPSVC_DISABLED=STUP0010W: The Startup Beans service is disabled due to previous errors. 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. Try to resolve the previously logged errors. If unable to do so, contact IBM product support. STARTUPSVC_STOPPED=STUP0013I: The Startup Beans service has stopped. The Startup Beans service has stopped and will be unable to process any Startup Beans. No user action required. STARTUPSVC_STOPPING=STUP0012I: The Startup Beans service is stopping. The Startup Beans service is stopping and will be unable to process any Startup Beans. No user action required. STARTUPSVC_STARTED=STUP0011I: The Startup Beans service started successfully. The Startup Beans service was started and is ready to process all Startup Beans. No user action required. STARTUPSVC_INIT=STUP0015I: The Startup Beans service has successfully initialized. The Startup Beans service has successfuly initialized. No user action required. ERR_FORCESTOP=STUP0005E: Startup bean named {0} forced application to stop. The specified startup bean start method returned "false" causing the application start to be aborted. Determine why the startup bean returned "false" and correct the problem allowing the application to start. FATAL_UNEX_EXCEPT=STUP9999E: Unexpected Exception Occurred: {0}. This exception is unexpected. The cause is not immediately known. 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/ . ERR_INVALIDTXTYPE=STUP0002E: Startup bean methods must not be marked as TX_MANDATORY {0} {1}. The transaction setting for the start and stop methods on a startup bean must not be marked as TX_MANDATORY. Mark the stop and start methods with any transaction setting other than TX_MANDATORY. ERR_NAMINGEX=STUP0003E: NamingException looking up home for startup bean with JNDI name {0}, exception was {1}. An unexpected exception occurred looking up the home for the startup bean. Verify the EAR deploy worked correctly and that the beans were deployed. ERR_INITERR=STUP0007E: Problem initializing startup service {0}. The startup service failed to initialize. Verify the application server installation. ERR_CREATEERROR=STUP0004E: Cannot create startup bean named {0}, exception was {1}. An unexpected exception occurred creating an instance of the startup bean. Verify the EAR containing the startup bean deployed correctly.