|
Problem |
MustGather for problems with the WebSphere®
Application Server enterprise bean workload management component.
Gathering this information before calling IBM support helps familiarize
you with the troubleshooting process and saves you time. |
|
|
|
Solution |
Two types of workload management exist
for WebSphere Application Server:
- WebSphere plug-in workload management.
- EJB workload management.
The following content provides you with the
MustGather information for EJB workload management and shows you how to
enable tracing on workload management (WLM).
If you have already contacted support, continue to
the component-specific MustGather information. Otherwise, click: MustGather: Read first for all WebSphere Application Server
products.
EJB workload management specific MustGather
information
- Domain
configuration detail
- WLM client
information
- WLM and Object
Request Broker (ORB) traces
- Domain
configuration detail
- For all releases of V3.5 and
V4.0:
- The admin.config file located in the following directory:
- The product.xml file located in the following directory:
install_root/properties/com/ibm/websphere
|
|
- The XML export of your repository configuration
located in your specified directory.
Notes:
- If your problem involves a
horizontal-cloned environment, send the admin.config, tracefile,
nanny.trace, and product.xml file from
each node.
- If you are using a stand-alone Java™ 2
Platform, Enterprise Edition (J2EE™) client, also collect your
client-side product.xml file.
- For all releases of V5.0, V5.1, and
V6.0:
- Run the versionInfo command and
collect all of the .txt files created.
Run the following command from each Base instance:
Base_install_root/bin/versionInfo.sh/bat >
versionof_Base_node1.txt |
Run the following command from each Network Deployment (ND)
instance:
|
ND_install_root/bin/versionInfo.sh/bat >
versionof_ND_node.txt |
|
- Run the genVersionReport command and
collect all of the .txt files created.
Run the following command from each Base instance:
Base_install_root/bin/genVersionReport.bat/sh -format
html -file myBaseVersionReport.html -efixes -ptfs
-componentDetail |
Run the following command from each ND instance:
|
ND_install_root/bin/genVersionReport.bat/sh -format
html -file myNDVersionReport.html -efixes -ptfs -componentDetail |
|
- Collect the entire configuration directories for
each Base and ND instance. Then create a separate .zip or .tar file for
each instance.
- For V5.0 and V5.1:
Base_install_root/config
ND_install_root/config |
|
- For V6.0:
Base_install_root/profiles/server_profile_name/config
Base_install_root/profiles/dmgr_profile_name/config |
Note: If you
are using a stand-alone J2EE client, collect client-side versionInfo as well.
|
- WLM client
information
Collect the following information:
- What .jar files are on your client machine?
- What are the locations of your .jar files?
- Did you install WebSphere Client or WebSphere
Application Server on the client side?
- How are you launching the client? Provide
step-by-step instructions.
- Do you launch your client with the launchClient utility from
the install_root/bin directory?
- If yes, then place the launchClient command in the
startup file (.bat or .sh). If it already exists in the startup file,
collect a copy of your startup file.
- Are you using a startup file (.bat or .sh)?
- If yes, collect your startup .bat file.
- Collect the environment settings. From where the
client is running, run a set >
environment.log command from the command
line prompt.
- If there appears to be a problem with the wrong
classes being loaded, or the wrong Java 2 SDK (J2SDK™)/Java Development
Kit (JDK™), perform the following:
- Try to unset the PATH and CLASSPATH before running
the launchClient command. If this action solves your problem, correct the
system PATH and CLASSPATH to use J2SDK/JDK and the other classes installed
by WebSphere Application Server .
- If the WebSphere Application Server is running a
different version of WebSphere Application Server than the client, use the
fix pack installation script to upgrade your client and server. Do not
manually copy files from any WebSphere Application Server directories.
- To understand which classes your client is
loading, review the LaunchClient.bat and setupCmdLine.bat files. Also, the setupClient.bat is used for thin clients.
- WLM and ORB
trace
- Server trace:
- Administrative server WLM, ORB and naming trace.
AND
- Request of the client.
- Client trace:
- WLM, ORB and naming trace from the Application
Server that makes the request
OR
- Stand-alone enterprise bean /Java/J2EE
Note: If you do not know how to set these
traces, see Appendix A.
Appendix
A:
The following details the steps you must take to
obtain the level of trace that you need for the following versions of
WebSphere Application Server:
Level of trace that you
need to set in V3.5 (all releases)
- Administrative server
trace:
Gather the following information from all
the nodes that participate in EJB workload management.
- Make sure that the default server and
administrative server are not running.
- Make a backup copy of your
admin.config file.
- Add the following lines to your
admin.config file:
com.ibm.CORBA.Debug=true
com.ibm.CORBA.CommTrace=true
#Note:Following trace string must be entered as one line and
there is ":" between trace strings
com.ibm.ejs.sm.adminServer.traceString=
com.ibm.ejs.wlm.*=all=enabled:com.ibm.ws.naming.*=all=enabled:
ORBRas=all=enabled
#
com.ibm.ejs.sm.adminServer.traceOutput=<WAS_Home>/logs/admin.trace |
|
- Save your admin.config file.
- Recycle your administrative server.
- Application Server and clone trace:
Gather the following information from all
of your clones that participate in EJB workload management.
- Make sure that your administrative server is
running and then start your administrative console.
- Enter the following line in the Command line arguments field
of the Application Server:
-Dcom.ibm.CORBA.Debug=true
-Dcom.ibm.CORBA.CommTrace=true |
|
- Click Apply and wait for the
completion message.
- Enter the following information in the
Trace specification field on the Advance tab of your
Application Server:
com.ibm.ejs.wlm.*=all=enabled:com.ibm.ws.naming.*=all=enabled:
ORBRas=all=enabled |
|
- Enter the following line in the Trace output file field on
the Advance tab of your Application Server:
$WAS_HOME\logs\MyClone.trace |
|
- Click Apply and wait for the
completion message.
- Recycle your Application Server to enable
tracing.
- Client trace:
- For a stand-alone Java client
- In your file,
install_root\properties\TraceSettings.properties, change the line at the bottom
of your file.
From:
com.ibm.ejs.ras.*=all=enabled |
|
To: |
|
com.ibm.ejs.wlm.*=all=enabled:com.ibm.ws.naming.*=all=
enabled:ORBRas=all=enabled |
Note: The
previous trace string must be entered as one line with a colon
(:) between trace
strings.
|
- Start the client program with '-D' arguments to
specify the trace settings.
Example:
java
-Dcom.ibm.CORBA.Debug=true
-Dcom.ibm.CORBA.CommTrace=true
-DtraceSettingsFile=TraceSettings.properties <clientProgram> |

|
- Application Server as a
client
Follow the same explanation in the
procedure, Application Server and clone trace.
Level of trace that you need
to set in V4.0 (all releases)
- Administrative server
trace:
- Make sure that your Application Server and
administrative server are not running.
- Make a backup copy of
the admin.config file located in
the install_root/bin directory.
- Edit and append the following lines to your
admin.config file:
com.ibm.CORBA.Debug=true
com.ibm.CORBA.CommTrace=true |
|
- Edit the # Trace settings to look like the
following example:
#Note: Following trace string must be
entered as one line and there is a colon (:)
between trace strings
com.ibm.ejs.sm.adminServer.traceString=com.ibm.ws.wlm.*=all=enabled:
com.ibm.ws.naming.*=all=enabled:ORBRas=all=enabled
#
com.ibm.ejs.sm.adminServer.traceOutput=<WAS_Home>/logs/admin.trace |
|
- Save your admin.config file.
- Recycle your administrative server to enable
tracing.
- Application Server and clone trace:
Collect the following information for all
of your clones that participate in EJB workload management.
- Make sure that your administrative server is
running and then start your administrative console.
- Highlight your Application Server, then select
the Services tab.
- Select OBJECT
REQUEST BROKER, then click Edit Properties.
- Select the Enable
ORB Tracing check box.
- Click OK.
- Click Apply.
- Click the Services tab, then
click Trace Service > Edit Properties. Place the
following information in the Trace
Specification field:
com.ibm.ws.wlm.*=all=enabled:
com.ibm.ws.naming.*=all=enabled:
ORBRas=all=enabled |
Note: The
preceding trace string must be entered as one line and there is a colon
(:) between
trace strings.
|
- Enter the fully qualified name in the
Trace Output field.
For example:
C:\WebSphere\AppServer\logs\MyAppServer.trace |
|
- Click Apply and wait for a
completion message.
- Recycle the Application Server to enable
tracing.
- Client trace:
- For a stand-alone Java client
- In the file,
install_root\properties\TraceSettings.properties, change the line at the bottom
of the file.
From:
com.ibm.ejs.ras.*=all=enabled |
|
To: |
|
com.ibm.ws.wlm.*=all=enabled:
com.ibm.ws.naming.*=all=enabled:
ORBRas=all=enabled |
Note: The
preceding trace string must be entered as one line with a colon
(:) between trace
strings.
|
- Start your client program with '-D' arguments to
specify the trace settings.
Example:
java
-Dcom.ibm.CORBA.Debug=true
-Dcom.ibm.CORBA.CommTrace=true
-DtraceSettingsFile=TraceSettings.properties <clientProgram> |
|
- For a J2EE client
Use the following steps to collect a J2EE
client trace:
- Copy
install_root\bin\launchClient from the client side to a backup file.
- Edit the following two trace parameters to the
following $JAVA_HOME/bin/java statement:
-Dcom.ibm.CORBA.Debug=true
-Dcom.ibm.CORBA.CommTrace=true |
|
Example: |
|
%JAVA_HOME%\bin\java
%CONSOLE_ENCODING% %CLIENTSAS%
-Dcom.ibm.CORBA.Debug=true
-Dcom.ibm.CORBA.CommTrace=true
-Dserver.root=%WAS_HOME% -Dws.ext.dirs=%WAS_EXT_DIRS%
-Dcom.ibm.CORBA.BootstrapHost=%COMPUTERNAME%
-Djava.naming.factory.initial=%NAMING_FACTORY% -classpath
%WAS_CLASSPATH% com.ibm.ws.bootstrap.WSLauncher
com.ibm.websphere.client.applicationclient.launchClient %* |
 |
- Start the launchClient with
trace:
CCtrace=com.ibm.ws.wlm.*=all=enabled:
com.ibm.ws.naming.*=all=enabled:
ORBRas=all=enabled |
|
Example: |
|
ClientSide_install_root\bin>
launchClient <your_ear_name.ear>
-CCtrace=com.ibm.ws.wlm.*=all=enabled:
com.ibm.ws.naming.*=all=enabled:
ORBRas=all=enabled
-CCtracefile=ClientSideTrace.txt |

|
- Application server as a
client
Follow the explanation in the
procedure, Application
Server and clone trace.
Level of trace that you need
to set for V5.0 and V6.0 (all releases)
In all releases of WebSphere Application Server V5.0,
you can perform the naming lookup at different levels. Based on the lookup
you might need to set server-side traces.
- Server trace:
The following process applies to your
dmgr, node agent and any application server.
- Setting the ORB Trace flag
- Through your administrative
console:
- Go to the Configuration page for the server to
trace.
For Application Server select
V5: Servers > Application Servers > server_name > Configuration Tab
V6: Servers > Application
Servers > server_name> Configuration Tab > Container Services > ORB
Service
V5: For NodeAgents select
V5: System
Administration-->Node Agents-->MyNodeAgent-->Configuration
Tab
V6: System Administration-->Node
Agents-->MyNodeAgent-->Configuration Tab->Container
Services->ORB Service
For DeploymentManager select
V5: System Administration
-->DeploymentManager-->Configuration Tab
V6: System Administration
-->DeploymentManager-->Configuration Tab->Container
Services->ORB Service
- Click ORB
Service under Additional Properties.
- Select the check box for ORB tracing under
General Properties.
- Through the server.xml
file
In a Network Deployment environment,
always edit the file in the Network Deployment install_root directory. Do
not edit the file in the Base install_root directory.
- Copy the server.xml file from the server that you are tracing to a backup file.
Example: For
a V5 single-server installation, the file is located at:
$WAS_HOME/config/cells/<cellName>/nodes/<nodeName>/servers/server1/server.xml
For a V6 single-server installation, the file is located at:
$WAS_HOME/profiles/<dmgr profile
name>/config/cells/<cellName>/nodes/<nodeName>/servers/server1/server.xml
- Edit the server.xml file.
- Search for
"orb:ObjectRequestBroker". The search
points you to the ORB service section.
- Edit (or add) the
'commTraceEnabled' attribute and set
it to true.
commTraceEnabled="true"
Example:
<services
xmi:type="orb:ObjectRequestBroker"xmi:id="ObjectRequestBroker_1"
enable="true"
requestTimeout="180" requestRetriesCount="1"
requestRetriesDelay="0" connectionCacheMaximum="240"
connectionCacheMinimum="100"
commTraceEnabled="true"locateRequestTimeout="180"
forceTunnel="never"
noLocalCopies="false">
- Save your file.
- Setting ORB, WLM and naming trace
strings
- Through your administrative
console:
- Start your Web console.
- Expand the following view:
-Troubleshooting
Logs and Trace
Configuration Problems
PMI Request Metrics
- Select Logs and Trace.
- Select the server you want to trace (In a Network
Deployment environment you need to set the traces for dmgr, nodeagent and
application server).
- Select Diagnostic
Trace.
- Click the Configuration tab.
- For V5, enter the following information in
Trace specification:
Naming=all=enabled:WLM=all=enabled:ORBRas=all=enabled
|
|
- For V6, the Trace Specification is at
Logs and Trace > server_name> Change Log
Detail Levels.
- Make sure to select File (radio button) in
Trace Output and
accept the default values.
- Click Apply.
- Save your changes and make sure to Synchronize changes with Nodes.
- Through the server.xml
file
In a Network Deployment environment,
always edit the file in your Network Deployment $WAS_HOME directory. Do
not edit the file in your Base $WAS_HOME directory.
- Copy the server.xml file from the server that you are tracing to a backup file.
Example: For
a V5 single-server installation, the file is located at:
$WAS_HOME/config/cells/<cellName>/nodes/<nodeName>/servers/server1/server.xml
For a V6 single-server installation, the file is located at:
$WAS_HOME/profiles/<dmgr profile
name>/config/cells/<cellName>/nodes/<nodeName>/servers/server1/server.xml
- Edit the server.xml file.
- Search for
"traceservice:TraceService". The search
points you to the Trace service section.
- Edit the
'startupTraceSpecification' attribute and set
it to:
Naming=all=enabled:WLM=all=enabled:ORBRas=all=enabled
Example:
<services
xmi:type="traceservice:TraceService"
xmi:id="TraceService_1" enable="true"
startupTraceSpecification="Naming=all=enabled:WLM=all=enabled:ORBRas=all=enabledtraceOutputType="SPECIFIED_FILE"
traceFormat="BASIC"
memoryBufferSize="8">
- Save your file.
- Client Trace:
Multiple clients are supported;
review the following information at: http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp
Select your edition of WebSphere Application Server, then select
- All topics by feature
- Applications
- Client modules
- Using application clients
- For a stand-alone Java
client
- In the file
$WAS_HOME\properties\TraceSettings.properties file, change the line at the
bottom of the file:
From: com.ibm.ejs.ras.*=all=enabled
To: com.ibm.ws.wlm.*=all=enabled:com.ibm.ws.naming.*=all=enabled:
ORBRas=all=enabled
#Note: Enter the previous trace string as one
line, with a colon (:) between trace strings.
- Start your client program with '-D' arguments to
specify the trace settings:
Example:
java
-Dcom.ibm.CORBA.Debug=true
-Dcom.ibm.CORBA.CommTrace=true
-DtraceSettingsFile=TraceSettings.properties <clientProgram>
- For a J2EE client
Use the following steps to collect a J2EE
client trace:
- Copy <ClientSide_$WAS_HOME>\bin\launchClient to a backup
file.
- Edit the following two trace parameters to the
following "$JAVA_HOME/bin/java" statement:
-Dcom.ibm.CORBA.Debug=true
-Dcom.ibm.CORBA.CommTrace=true
Example:
"%JAVA_HOME%\bin\java" %CONSOLE_ENCODING%
"%CLIENTSAS%"
"%CLIENTSOAP%" %ORB_RAS_MGR% -Dwas.install.root="%WAS_HOME%"
-Dws.ext.dirs="%WAS_EXT_DIRS%" %JAAS_LOGIN_CONFIG%-Dcom.ibm.CORBA.Debug=true
-Dcom.ibm.CORBA.CommTrace=true
-Dcom.ibm.CORBA.BootstrapHost=%DEFAULTSERVERNAME%
-Dcom.ibm.CORBA.BootstrapPort=%SERVERPORTNUMBER%
-Djava.naming.factory.initial=%NAMING_FACTORY% %USER_INSTALL_PROP%
-Xbootclasspath/p:"%WAS_BOOTCLASSPATH%" -classpath
"%WAS_CLASSPATH%" com.ibm.ws.bootstrap.WSLauncher
com.ibm.websphere.client.applicationclient.launchClient %*
- Start your launchClient with trace:
CCtrace=com.ibm.ws.wlm.*=all=enabled:com.ibm.ws.naming.*=all=enabled:
ORBRas=all=enabled
Example:
<ClientSide_$WAS_HOME>\bin> launchClient <customer.ear> -CCtrace=com.ibm.ws.wlm.*=all=enabled:com.ibm.ws.naming.*=all=enabled:ORBRas=all=enabled-CCtracefile=ClientSideTrace.txt
LaunchClient toolhttp://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/rcli_javacmd.html
Application client troubleshooting
tipshttp://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/rcli_troubleshoot.html
- Application server as a client
Follow the explanation from the
procedure, Server trace.
Follow instructions to send diagnostic information to IBM support.
For a listing of all technotes, downloads, and
educational materials specific to the Workload Management (WLM) component,
search the WebSphere Application Server support site. |
|
|