Troubleshooting
Problem
Collecting data for WebSphere Compute Grid problems with IBM WebSphere Application Server. Gathering this information before calling IBM support will help familiarize you with the troubleshooting process and save you time.
Resolving The Problem
Tab navigation
- Learning more
- Troubleshooting
- Collecting data- selected tab,
Collecting data for WebSphere Compute Grid(Java Batch)problems with IBM WebSphere Application Server. Gathering this information before calling IBM support will help familiarize you with the troubleshooting process and save you time.
MustGather: Read first for WebSphere Application Server
For a list of all technotes, downloads, and educational materials, search the WebSphere Application Server support site.
Troubleshooting guide for WebSphere Application Server
Steps to get support for WebSphere Application Server
The batch environment uses the WebSphere Application Server logging and tracing system.
Gather the following traces if you encounter any problems in your Compute Grid(Java Batch) environment:
On the Scheduler server(s) enable following trace
com.ibm.ws.batch*=all:com.ibm.ws.grid*=all
On the Endpoint server(s) enable following trace
com.ibm.ws.batch*=all:com.ibm.ws.grid*=all:com.ibm.ws.ci.*=all
In addition to collecting the traces , please gather the following:
- Job logs - A job log is a file that contains a detailed record of the execution details of a job. System messages from the batch container and output from the job executables are collected. Job logs are located in WAS_PROFILE_ROOT/joblogs directory.
If using external scheduler, collect the job logs of external scheduler as well. On z/OS this would be the JES job log of the JES job that launched the Compute Grid job by calling WSGRID. On other platforms there may be analogous external scheduler logs, even if it is not integrated into the Operating System.
- Run the collector tool against the Deployment Manager Profile to produce a JAR file containing your WebSphere Application Server configuration files and other logs that are useful to the WebSphere Application Server support team.
Gathering information with the collector tool-V9.
Gathering information with the collector tool - V8.0 and V8.5
Gathering information with the collector tool - V7.0
- Gather all the JVM logs from the Scheduler and Endpoint servers, namely SystemOut.log, SystemErr.log, and the native stdout and stderr log files.
WebSphere Application Server 9.0 JVM Logs
WebSphere Application Server 8.5.5 JVM Logs
WebSphere Application Server 8.0 JVM Logs
WebSphere Application Server 7.0 JVM Logs
- Gather all the First Failure Data Capture (FFDC) files. The FFDC files are in the ffdc subdirectory at the same location as the JVM logs.
- Follow instructions to send diagnostic information to IBM support to send the files mentioned in the preceding steps.
For a listing of all technotes, downloads, and educational materials specific to Compute Grid, search the
WebSphere Application Server support site
Related information
Submitting information to IBM support
Steps to getting support for WebSphere Application Server
MustGather: Read first for WebSphere Application Server
Troubleshooting guide for WebSphere Application Server
To diagnose or identify a problem, it is sometimes necessary to provide Technical Support with data and information from your system. In addition, Technical Support might also need to provide you with tools or utilities to be used in problem determination. You can submit files using one of following methods to help speed problem diagnosis:
- IBM Support Assistant (ISA)
- Service Request (SR)
- FTP to the Enhanced Customer Data Repository (ECuRep)