An exception aa....aa was raised in initialization of the servlet class bb....bb. (J2EE application = cc....cc, context root = dd....dd)

aa....aa: Exception name
bb....bb: Class name
cc....cc: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode
dd....dd: Context root name

Description

An exception occurred during servlet initialization.

The exception might have occurred in the following processes:

• Class loading
• Instantiation
• init processing of the servlet
• Dependency Injection processing

Action

Remove the cause due to which an exception occurred during the initialization of the servlet. The stack trace is output in the Web servlet log. For details on the Web servlet logs, see 4.3.1 Aquiring the Cosminexus Component Container Logs in the uCosminexus Application Server Maintenance and Migration Guide.

If an error occurs in the processing of the Dependency Injection, an error message is output just before this message. The output destination is the message log. Check, and then take action.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.