|
Problem(Abstract) |
MustGather for problems with the WebSphere® Application
Server Work Area component, a Programming Model Extension (PME) that is
available in WebSphere Application Server V5 Enterprise Edition, WebSphere
Business Integration Server Foundation (WBI SF) V5.1, and all editions of
WebSphere Application Server V6.0. Gathering this information before
calling IBM® support will help familiarize you with the troubleshooting
process and save you time. |
|
|
|
Resolving the
problem |
If you have already contacted support, continue on to the
component-specific MustGather information. Otherwise, click: MustGather:
Read first for all WebSphere Application Server products.
Work Area specific MustGather Information
- What is the exact version and the edition (i.e. Base, Enterprise, WBI
SF, ND) of WebSphere Application Server that is installed?
- Provide a full description of the problem that you've encountered,
including the stack traces of any errors or exceptions that are occurring.
Provide any logs that contain the errors or exceptions. These can usually
be found in the install root/logs directory.
- Under what circumstances does the problem occur? Does it occur every
time a certain task is done or does it occur intermittently? Has this
problem always occurred? If not, was a change recently made before the
problem started to occur?
- Send the SystemOut.log for the application server on which the Work
Area problem occurs:
- For V6, located in the
install_root/profiles/profile_name/logs/server_name
directory
- For V5, located in the
install_root/logs/server_name directory
- Enable tracing:
- For V6:
- In the WebSphere Administrative Console, expand "Troubleshooting" and
select "Logs and Trace"
- In the "Logging and Tracing" page, select your server and then
"Diagnostic Trace"
- Ensure that "Enable Log" is checked
- Under "Trace Output", select "File", and accept the defaults
- Click OK and save your configuration
- Again expand "Troubleshooting" and select "Logs and Trace"
- In the "Logging and Tracing" page, select your server and then "Change
Log Detail Levels"
- Enter the following trace string:
*=info:com.ibm.ws.workarea.*=all:ActivityService=all
- Click OK and save your configuration
- Restart the Application Server
- Recreate the problem
- Send the resulting trace output file
- For V5.1 and V5.0:
- In the WebSphere Administrative Console, expand "Troubleshooting" and
select "Logs and Trace"
- In the "Logging and Tracing" page, select your server and then
"Diagnostic Trace"
- Ensure that "Enable trace with the following specification" is
checked
- In the "Trace Specification" field, enter:
com.ibm.ws.workarea.*=all=enabled:ActivityService=all=enabled
- Under "Trace Output", select "File", and accept the defaults
- Click OK and save your configuration
- Restart the Application Server
- Recreate the problem
- Send the resulting trace output file
- Run
the collector tool to produce a JAR file containing your WebSphere
configuration files and other logs that are useful to the WebSphere
Application Server support team.
- Follow instructions to send
diagnostic information to IBM support to send the SystemOut.log, the
trace output file, and the collector output.
For a listing of all technotes, downloads, and educational materials
specific to the Work Area component, search the WebSphere
Application Server support site or the WBI
Server Foundation support site. |
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|