STUP

STUP0001E: Message key {0} was not found in any searched resource bundles.

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.

STUP0002E: Startup bean methods must not be marked as TX_MANDATORY {0} {1}.

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.

STUP0003E: NamingException looking up home for startup bean with JNDI name {0}, exception was {1}.

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.

STUP0004E: Cannot create startup bean named {0}, exception was {1}.

Explanation

An unexpected exception occurred creating an instance of the startup bean.

Action

Verify the EAR containing the startup bean deployed correctly.

STUP0005E: Startup bean named {0} forced application to stop.

Explanation

The specified startup bean start method returned "false" causing the application start to be aborted.

Action

Determine why the startup bean returned "false" and correct the problem allowing the application to start.

STUP0006E: Exception calling startup bean named {0}, exception was {1}

Explanation

An unexpected exception occurred calling the start or stop method of the startup bean.

Action

Verify why the method throws an exception.

STUP0007E: Problem initializing startup service {0}.

Explanation

The startup service failed to initialize.

Action

Verify the application server installation.

STUP0008I: The Startup Beans service is disabled.

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.

STUP0009I: The Startup Beans service cannot be disabled.

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.

STUP0010W: The Startup Beans service is disabled due to previous errors.

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.

STUP0011I: The Startup Beans service started successfully.

Explanation

The Startup Beans service was started and is ready to process all Startup Beans.

Action

No user action required.

STUP0012I: The Startup Beans service is stopping.

Explanation

The Startup Beans service is stopping and will be unable to process any Startup Beans.

Action

No user action required.

STUP0013I: The Startup Beans service has stopped.

Explanation

The Startup Beans service has stopped and will be unable to process any Startup Beans.

Action

No user action required.

STUP0014E: The Startup Beans service could not resolve the {0} service.

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. Contact IBM product support if you are unable to correct the problem.

STUP0015I: The Startup Beans service has successfully initialized.

Explanation

The Startup Beans service has successfuly initialized.

Action

No user action required.

STUP0016W: Startup Bean {0} has a wasStartupPriority value with an incorrect type.

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.

STUP9999E: Unexpected Exception Occurred: {0}.

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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J .