TroubleShooting: WebSphere Compute Grid Problems for WebSphere Application Server

Resolving The Problem

TroubleShooting steps to help resolve WebSphere Compute Grid problems

In this section you will find common WebSphere Compute Grid problems & solutions that may help resolve your Compute Grid problems.

Blogs:
WebSphere Java Batch common issues and how to troubleshoot
How to Configure Java Batch environment in WebSphere V8.5

WSTE:
Webcast: WebSphere Application Server Java Batch concepts, configuration, troubleshooting and common issues
Webcast Replay: Overview of Batch features in WebSphere V8.5.x

SupportTV videos:
How to configure Compute Grid in WebSphere Application Server V8.5.5 and later versions
How do I configure WSGrid in WebSphere Application Server v8.5.5 and later versions?
Configuring the Java batch job scheduler through the admin console in WAS

Common Compute Grid Problems and their solution



Debugging connectivity issues between the lrcmd.sh|bat client and the server:

If any connection problems happens between the client side lrcmd.sh|bat script and the Application Server, please first try to use the HTTPs port instead the HTTP port.

For further debugging the following instructions can be tried:

Enabling traces when using lrcmd.sh|bat:

1. Pick a directory, say /mytrace and copy file $WAS_HOME/properties/TraceSettings.properties to it as /mytrace/batch.trace.properties.

2. Edit contents of this trace properties file:

one line with exact trace spec:
com.ibm.*=all:org.apache.*=all

another line with trace file name (or stdout):
traceFileName=c:/MyTraceFile.log # (or stdout)

3. Edit script lrcmd.sh/lrcmd.bat (best is to copy to mylrcmd.sh/mylrcmd.bat),
copying it to the $WAS_HOME/bin directory or the <profile_root>/bin directory. Add the directory containing your trace properties file to the classpath by changing to:

Unix:
C_PATH=$WAS_HOME/runtimes/com.ibm.ws.webservices.thinclient_9.0.jar:$WAS_HOME/plugins/com.ibm.ws.batch.runtime.jar:/mytrace

Windows:
set CLASSPATH=%WAS_HOME%/runtimes/com.ibm.ws.webservices.thinclient_9.0.jar;%WAS_HOME%/plugins/com.ibm.ws.batch.runtime.jar;C:/mytrace


4. Export javaoption shell variable:

From Unix shell (or cygwin):
export javaoption="-DtraceSettingsFile=batch.trace.properties"

Please notice: Base name only, does NOT include directory name

From Windows cmd:
set javaoption="-DtraceSettingsFile=batch.trace.properties"

Note:
For each platform, you would append any other space-separated props. within the double-quoted string. Do this rather than trying to use -javaoption on the CLI. For example:
export javaoption="-DtraceSettingsFile=batch.trace.properties -DsomeOtherProp=someOtherVal"

5. Run your mylrcmd.sh with the normal options. For example:
../mylrcmd.sh -host=localhost -port=9082 -debug -cmd=getJobsByClass -class=Default




Enabling traces when using WSGrid.sh|bat:

1. Pick a directory, say /mytrace and copy file $WAS_HOME/properties/TraceSettings.properties to it as /mytrace/batch.trace.properties.

OR:

if $WAS_HOME/properties is writable, you could copy to $WAS_HOME/properties/batch.trace.properties and avoid the need to copy/edit the script in step 3 below.

2. Edit contents of trace properties file above. One line with exact trace spec. For example:
com.ibm.*=all:WSGrid=all

another line with trace file name (or stdout):
traceFileName=c:/MyTraceFile.log # (or stdout) - Note the forward slash in c:/...

3. Add the directory containing your properties file to script classpath (if you didn't use $WAS_HOME/properties). For this you will have to edit WSGrid.bat/WSGrid.sh (best is to copy to myWSGrid.bat/myWSGrid.sh), copying it to the $WAS_HOME/bin directory or the <profile_root>/bin directory.

An easy way is to locate this line:
JMS_PATH=$WAS_HOME/lib/WMQ/java/lib/com.ibm.mq.jar:$WAS_HOME/lib/WMQ/java/lib/com.ibm.mqjms.jar:$WAS_HOME/lib/WMQ/java/lib/dhbcore.jar

then add this new line:
JMS_PATH=$JMS_PATH:/mytrace # Use ';' path separator on Windows

4. Windows only - edit script WSGrid.bat
- Comment out this line
@REM set javaoption=

5. Export javaoption shell variable:

From Unix shell (or cygwin):
export javaoption="-DtraceSettingsFile=batch.trace.properties" # Base name only, does NOT include directory name

From Windows cmd:
set javaoption="-DtraceSettingsFile=batch.trace.properties" # (or TraceSettings.properties if you used that)

Note:
For each platform, you would append any other space-separated props. Do this rather than trying to use -JVMOptions on the CLI. E.g:
export javaoption="-DtraceSettingsFile=batch.trace.properties -DsomeOtherProp=someOtherVal"

6. Run your myWSGrid.sh (myWSGrid.bat) normally. For example:
../myWSGrid.sh ctrl.props job.xml



What to do Next?
If the preceding troubleshooting steps did not solve your problem, see the MustGather for WebSphere Compute Grid problems to continue investigation.