Enabling JMS trace for releases of WebSphere Application Server V5.0 and V6.0
 Technote (troubleshooting)
 
Problem(Abstract)
To debug Java™ Message Service (JMS) problems, it is very useful to collect a trace of the failure. This technote provides instructions on how to enable JMS trace for releases of IBM® WebSphere® Application Server V5.0 and V5.1
 
Resolving the problem
1. Bring up the WebSphere Administrative Console and log in.

2. In the left hand tree view, click Troubleshooting -> Logs and Trace.

3. When the Logging and Tracing panel appears, select the name of the server or servers that you wish to enable trace for from the Server / Node / Type list.

For example in a Network Deployed environment you may see jmsserver and server1 for the default application server.

Depending on where the problem is you may select and choose trace options for one or more of these. If you have a question about which server needs to be traced then contact the support team that requested the traces for more information.

4. Navigation

WebSphere Application Server V5.0
Click on the Diagnostic Trace option in the Logging and Tracing table.
Under the Trace Specification option, click on the Modify button.

WebSphere Application Server V6.0
Click on the Change Log Detail Levels option in the Logging and Tracing table.

*NOTE**
To ensure you capture full data flows, select Trace Output Format = Advanced



5. You should now see the Diagnostic Trace service panel. Enter the following string into the Trace Specification field:
WebSphere Application Server V5.0 (all on one line)
JMSApi=all=enabled:JMSServer=all=enabled:JMSQueueManager=
all=enabled:Messaging=all=enabled:

WebSphere Application Server V6.0 (all on one line)
*=info:JMSApi=all:JMSServer=all:Messaging=all:JMS_WASTraceAdapter
=all: com.ibm.mq.*=all:
(Note: The above trace parameters will enable both JMS Wrapper and JMS Server trace)

You may also be requested by the level 2 or level 3 support teams to gather a transaction and connection API trace. If this is required then append the following string to the Trace Specification field:


WebSphere Application Server V5.0
ConnLeakLogic=all=enabled:WAS.j2c=all=enabled   -- For Connection
Transaction=all=enabled     -- For Transaction


WebSphere Application Server V6.0
ConnLeakLogic=all:com.ibm.ejs.j2c.*=all   -- For Connection
com.ibm.ws.Transaction.*=all   -- For Transaction

6. Click OK and restart the Application Server for the new tracing to take effect.

7. The trace information will be written to the file
WebSphere Application Server V5.0
<WAS_HOME>\logs\<server_name>\trace.log.

WebSphere Application Server V6.0
<WAS_HOME>\profiles\<server_name>\logs\<server_name>\trace.log

Sometimes it will be necessary to capture the JMS Client trace (which includes Distribution Hub, or disthub, trace). To enable JMS client trace, follow the following steps:
1. Expand the servers entry in the left hand tree view, and click on the Application Servers link.

Note:The Application Servers panel will now appear, containing a list of application servers. Click on the same application server that you selected previously.

2. Navigation
WebSphere Application Server V5.0
In the next panel, click on the Process Definition link within the Additional Properties table.
WebSphere Application Server V6.0
Expand Java and Process Management (under Server Infrastructure) and click on Process Definition link
3. The Process Definition panel should now appear. Click on the Java Virtual Machine link. In the Generic JVM™ arguments field, enter:

-DMQJMS_TRACE_LEVEL=base


Note:
This will turn on JMS Client tracing (which includes Distribution Hub, or disthub, trace).
4. Click OK and save the configuration changes.

5. Logoff the Administrative Console and restart the Application Server for which trace has been enabled.

Once you have captured the trace, the trace should be switched off. To do this:
1. Bring up the WebSphere Administrative Console and log in.

2. In the left hand tree view, click Troubleshooting -> Logs and Trace.

3. When the Logging and Tracing panel appears, select the name of the server or servers that you wish to disable trace on.

4. Navigation
WebSphere Application Server V5.0
Click on the Diagnostic Trace option in the Logging and Tracing table.
Under the Trace Specification option, click on the Modify button.
WebSphere Application Server V6.0
Click on the Change Log Detail Levels option in the Logging and Tracing table.
5. You should now see the Diagnostic Trace service panel. Ensure that the Trace Specification field is set to the following:
WebSphere Application Server V5.0
<blank>
WebSphere Application Server V6.0
*=info
6. Click OK and restart the application server.

To disable the JMS Client tracing, the following steps should be carried out:
1. Expand the servers entry in the left hand tree view and click on the Application Servers link.

Note:The Application Servers panel will now appear, containing a list of application servers. Click on the same application server that you selected previously.

2. Navigation
WebSphere Application Server V5.0
In the next panel, click on the Process Definition link within the Additional Properties
table
WebSphere Application Server V6.0
Expand Java and Process Management (under Server Infrastructure) and click on Process Definition link
3. The Process Definition panel should now appear. Click on the Java Virtual Machine link. In the Generic JVM arguments field, remove the entry below:

-DMQJMS_TRACE_LEVEL=base

4. Click OK, and save the configuration changes

5. Logoff the Administrative Console, and restart the Application Server for which trace has been enabled


Note:

By default WebSphere creates a single 20MB trace file in the file ${SERVER_LOG_ROOT}/trace.log. Depending on the length of time that you collect the trace and the amount of trace output, you may want to increase both the size of each trace file and the number of trace files.

This is done by modifying the fields for the Maximum File Size and Maximum Number of Historical Files on the Trace Output panel when you are entering the trace strings in step 5 above.

In addition you may want to consider redirecting the output of the trace to another file system by modifying the File Name parameter ${SERVER_LOG_ROOT}/trace.log to point to a file system with more free space. Be aware that by doing so you may impact the performance of the system that is being traced.

 
Related information
MustGather: Readme first
Troubleshooting guide
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Java Message Service (JMS)
Operating system(s): Windows
Software version: 6.1
Software edition:
Reference #: 1199176
IBM Group: Software Group
Modified date: Feb 28, 2005