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

aa....aa: Exception name
bb....bb: 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
cc....cc: Context root name
dd....dd: Path of the JSP file or tag file within the Web application
(However, for a tag file saved in the JAR file, the output will be in the following format:
'Path within the Web application of the JAR file (entry = path-within-the-JAR-file)')

Description

An exception occurred during the initialization of JSP.

The exception might have occurred in the following processes:

• Class loading
• Instantiation
• init processing of JSP

Action

Remove the cause due to which an exception occurred during the initialization of JSP. The stack trace is output in the Web servlet log.

If the exception name is ClassNotFoundException, the loading of the class generated from JSP might have failed due to the following reasons.

• File read permission is not available.
• The file system has failed.
• Memory is insufficient.

Correct the error location depending on the reason, 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.