Chapter 2. Web container problem determination 97
򐂰 JSR-000152 JavaServer Pages 2.0 Specification, for issues related to
internationalization:
http://jcp.org/aboutJava/communityprocess/final/jsr152/index.html
򐂰 Internationalization: Resources for learning:
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topi
c=/com.ibm.websphere.base.doc/info/aes/ae/rin_resources.html
For current information available from IBM Support about known issues and
resolutions that are related to encoding, see:
http://www.ibm.com/support/search.wss?rs=180&tc=SSEQTP&tc1=SSCVRZX&rank
profile=8&dc=DB520+D800+D900+DA900+DA800&dtm
If these steps still do not resolve your problem, see “The next step” on page 99..
2.6 Collect diagnostic data
This section provides guidance for collecting log files and trace data that are
useful in diagnosing Web container problems.
2.6.1 JVM logs
JVM logs, often referred to as SystemOut and SystemErr logs, are created for
every WebSphere Application Server process (application server, cluster
member, node agent, and deployment manager). They can be found in the
following locations:
򐂰 WebSphere Application Server V6.x for IBM z/OS
The JVM logs are located in the address space output. Usually a section
labeled SYSOUT has diagnostic data from the JVM that runs in the servant
region.
򐂰 WebSphere Application Server V6.x (distributed and i5/OS)
The JVM log files are by default named SystemOut.log and SystemErr.log.
The default location for the SystemOut and SystemErr logs is:
profile_root/logs/server_name/SystemOut.log
profile_root/logs/server_name/SystemErr.log:
The location of application server logs is configurable.
1. Select Troubleshooting Logs and Trace in the navigation bar.
2. Click the server name.
3. Select JVM logs.

Get WebSphere Application Server V6.1 Problem Determination: IBM Redpaper Collection now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.