How to enable trace for the Embedded Messaging Broker in WebSphere Application Server V5.0
 Technote (troubleshooting)
 
Problem(Abstract)
The IBM® WebSphere® Embedded Messaging Publish & Subscribe Broker requires a different tracing method than other WebSphere components. When a problem exists with the broker, how can it be traced?
 
Resolving the problem
Follow these steps to enable tracing for the Broker:

  1. Set the trace specification JMSBroker=all=enabled in the WebSphere administrative console.
    1. In the console, expand Troubleshooting, click on Logs and Trace, select the server, then click Diagnostic Trace.
    2. Type JMSBroker=all=enabled in the Trace Specification field.
    3. Ensure that Enable Trace is checked, and type a Trace Output file name.
    4. Save the configuration and restart the server to start the trace.

  2. On UNIX® platforms only, run the setupmq.sh script in the WebSphere install root/bin directory. Set the following environment variables:
    • WEMPS_REGISTRY=/var/wemps/registry
    • For Linux®: LD_LIBRARY_PATH=<WebSphere install root>/java/jre/bin/classic
    • For Solaris: LD_LIBRARY_PATH=<WebSphere install root>/java/jre/lib/sparc/client

  3. Start the trace using the wempschangetrace command. Run the following command from the WEMPS install root/bin directory:

    wempschangetrace WAS_nodename_servername -t -e default -l debug -c 10000 -r -x FFFFFFFF-0000-0000-0000-000000000000

    Note: This command is on one line. node name and server name are the names of the server on which the Broker is running. Use jmsserver as the server name if running in WebSphere Network Deployment (ND).

  4. Reproduce the problem.

  5. Stop the trace using the wempschangetrace command. Run the following command from the WEMPS install root/bin directory:

    wempschangetrace WAS_<nodename>_<servername> -t -e default -l none -x FFFFFFFF-0000-0000-0000-000000000000

    Note: This command is on one line. node name and server name are the names of the server on which the Broker is running. Use jmsserver as the server name if running in WebSphere Network Deployment (ND).

  6. After reproducing the problem with the tracing enabled, two additional commands must be run to convert the trace into a readable form. Run both commands from the WEMPS install root/bin directory. Note that these commands must be run on the system where the trace was taken:

    wempsreadlog WAS_<nodename>_<servername> -t -x FFFFFFFF-0000-0000-0000-000000000000 -f -o WASlog.xml

    wempsformatlog -i WASlog.xml -o WASlog.out

    Note: The -i and -o options are input and output files so any file names can be used (instead of WASlog.xml and WASlog.out from the command), although the output file for wempsreadlog must match the input file for wempsformatlog.

Send the resulting WASlog.out to IBM support for analysis.
 
 
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: 5.1.1
Software edition:
Reference #: 1145847
IBM Group: Software Group
Modified date: Mar 29, 2007