|
Problem |
MustGather for problems with the WebSphere® Application
Server JSP component for all releases of V4.0. Gathering this information
before calling IBM® Support will help familiarize you with the
troubleshooting process and save you time. |
|
Cause |
Error in JSP. |
|
Solution |
If you have already contacted support, continue on to the
JSP MustGather information. Otherwise, click: MustGather:
Read first for all WebSphere Application Server products.
JSP specific MustGather information:
- Open the ibm-web-ext.xmi file located in the WEB-INF directory of the
WAR file. For example:
install_root\installedApps\app.ear\myapp.war\WEB-INF\ibm-web-ext.xmi |
|
- Add the following line right before the closing
</webappext:WebAppExtension> tag:
<jspAttributes
xmi:id="JSPAttribute_1" name="keepgenerated" value="true"/> |
|
- Open the adminstrative console.
- Stop the Application Server.
- Delete the contents of the following directory:
install_root\temp\node_name |
Where install_root is the directory that WebSphere is installed and
where node_name is the hostname of the server.
|
- Start the Application Server.
- Request the JSP from a browser, which will force the JSP to be
converted to Java™ and then compiled.
- Find the source code (.java files) of the generated JSPs in the
following directory:
- Look in the stdout file for the application server. It will show the
line number where the exception occurred. Go to the line number of the
.java file indicated in the exception to investigate root cause of JSP
failure.
- See the following technote:
Problem Determination: org.apache.jasper.JasperException: JSPG0059E:
Unable to compile class for JSP
- Follow instructions to send
diagnostic information to IBM support.
For a listing of all technotes, downloads, and educational materials
specific to the JSP component, search the WebSphere
Application Server support site. |
|
|