Procedure to take a user or service trace of message flow at an execution group level

Technote (troubleshooting)


Problem(Abstract)

Use this procedure to capture a user or service level trace of a WebSphere Message Broker message flow at an execution group level.

Gathering this information before calling IBM Support will help familiarize you with the troubleshooting process and save you time.

Resolving the problem

Service Level Trace : Service trace provides more detailed information than that provided by the entries that are written to the Syslogs, Event Logs, Trace Node Outputs, or User Trace. Typically, IBM support uses service trace for debugging problems as it can trace internal calls in addition to the brokers, execution groups, and deployed message flows.

User Level Trace : User trace provides more information than that provided by the entries that are written to the logs. Typically, you use user trace for debugging your applications, as it can trace brokers, execution groups, and deployed message flows.





Service Level Trace




1. Start trace.

mqsichangetrace <brokername> -t -e <egroup> -l debug -r -c 100000

2. Put a message on the queue to cause the failure to occur.

3. Stop trace.

mqsichangetrace <brokername> -t -e <egroup> -l none

4. Retrieve the trace log for the specified component.

mqsireadlog <brokername> -t -e <egroup> -f -o flowtrace.xml


5. Format the XML trace file.

mqsiformatlog -i flowtrace.xml -o serviceflowtrace.txt

The serviceflowtrace.txt will be in the current working directory.






User Level Trace



1. Start trace .
    mqsichangetrace <brokername> -u -e <egroup> -f "<Message Flow Name>" -l debug -r -c 50000

    <brokername> is the name of your broker
    <egroup>
    is the name of your execution group
    You can also start tracing, by going to Operations tab, and right click Message Flow, and click Start Trace

2. Put a message on the input node queue to cause the failure to occur.

3. Stop trace.

    mqsichangetrace <brokername> -u -e <egroup> -f "<Message Flow Name>" -l none

    You can also stop tracing, by going to Operations tab, and right click Message Flow, and click Stop Trace

4. Retrieve the trace log for the specified component.
    mqsireadlog <brokername> -u -e <egroup> -f -o flowtrace.xml

5. Format XML tracefile.
    mqsiformatlog -i flowtrace.xml -o userflowtrace.txt

The userflowtrace.txt will be in the current working directory.

Product Alias/Synonym

WMB MB WebSphere Message Broker MQ Integrator WBIMB WBI-MB MQSI WMQI

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere Message Broker
Execution Group

Software version:

6.0, 6.1, 7.0, 8.0

Operating system(s):

AIX, HP-UX, Linux, Solaris, Windows

Reference #:

1177321

Modified date:

2013-04-04

Translate my page

Machine Translation

Content navigation