|
Problem(Abstract) |
Collecting data for problems with IBM® WebSphere®
Application Server JSP container component. Gathering this MustGather
information before calling IBM support will help you understand the
problem and save time analyzing the data. |
|
|
|
Resolving the
problem |
If you have already contacted support, continue on to
begin collecting component-specific MustGather information. Otherwise,
click: MustGather:
Read first for all WebSphere Application Server products.
JSP specific MustGather information
- Run the JspBatchCompiler.sh or
JspBatchCompiler.bat on the failing JSP with
-keepgenerated option as per following version specific example.
The -keepgenerated option will generate _*.java file
while compiling JSP to _*.class file. To determine the
enterpriseapp.name and webmodule.name, see the section
below.
- For WebSphere Application Server V6.0 and 6.1:
Run the following JSPBatchComplier command:
install_root/profiles/profile_name/bin/JspBatchCompiler
-enterpriseapp.name
application_name -webmodule.name
webapplication_name -cell.name
cell_name -node.name
node_name -server.name
server_name -filename
jsp_file -keepgenerated true -forceCompilation
true -log.level FINEST > jspbatchcompiler.out
2>&1 |
|
- For WebSphere Application Server V5.0 and 5.1:
Delete compiled class _*.class for JSP from the following
directory before running JspBatchCompiler:
|
install_root/temp/node_name/server_name/EAR_name/WAR_name |
|
If you have selected the precompile option during
application install, you will find the compiled class for the JSP under
the following directory: |
|
install_root\installedApps\node_name\EAR_name\WAR_name\WEB-INF\classes |
|
Run the following JSPBatchComplier command: |
|
install_root/bin/JspBatchCompiler
-enterpriseapp.name
application_name -webmodule.name
webapplication_name -cell.name
cell_name -node.name
node_name -server.name
server_name -filename
jsp_file -keepgenerated true >
jspbatchcompiler.out 2>&1 |
|
|
Determining the enterpiseapp.name and
webmodule.name:
- In the Administrative Console, expand Applications and click
Enterprise Applications.
- For enterpiseapp.name, use the name of the enterprise
application as seen in the name field.
- Click on the enterprise application.
- For V6.0 Click Web Modules under Related Items.
For V6.1 Click Manage Modules under Modules
- For webmodule.name, use the name of the Web module as seen in
the url field for V6.0. For V6.1, use the name of Web
module under Module colom, make sure this to be web module by
checking under Module Type colom for that module row.
|
|
- Set up trace for Application Server using the following trace string.
For detailed instructions on setting trace, refer to How
to setup a trace? Note: You can skip this step if you have a
JSP compilation problem.
- For WebSphere Application Server V6.0 and
6.1:
*=info:com.ibm.ws.webcontainer.*=all
:com.ibm.wsspi.webcontainer.*=all:HTTPChannel=all
:GenericBNF=all:com.ibm.ws.jsp=all |
|
- For WebSphere Application Server V5.0 and
5.1:
Servlet_Engine=all=enabled:HTTP_Transport=all=enabled
:com.ibm.ws.webcontainer.jsp.*=all=enabled |
|
- Recreate the problem and send the following documents to support:
- Generated _*.java file from step 1
- Compiled _*.class file from step 1
- jspbatchcompiler.out from step 1
- Source file for failing JSPs
- All the files from server logs directory:
- SystemErr.log
- SystemOut.log
- native_stderr.log
- native_stdout.log
- trace.log
- The ffdc.log files generated during recreating
issue.
- The server.xml file from the following directory:
install_root\config\cells\cell_name\nodes\node_name
\servers\server_name |
|
- Follow instructions to send
diagnostic information to IBM support.
For a list of all technotes, downloads, and educational materials
specific to JSPs, search the WebSphere
Application Server support site. |
|
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
WebSphere Application Server - Express |
JSP |
AIX, HP-UX, Linux, Solaris, Windows |
6.0 |
|
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|