Technote (troubleshooting)
Problem(Abstract)
Use these procedures to take a startup trace of a broker or execution group in WebSphere Message Broker (WMB).
Gathering this information before calling IBM Support will help familiarize you with the troubleshooting process and save you time.
Resolving the problem
Trace Instructions
New trace features have been made available from WMB v7.0.0.3 and WMB v8.0.0.0 onwards.
- The new trace procedure uses mqsichangetrace. The new procedure is the preferred method of tracing if you are at or beyond these maintenance levels, UNLESS the problem is with WMB's configstore tables.
- The old trace procedure uses mqsiservice. You should use the old trace procedures if your system is prior to WMB V7.0.0.3 or if your problem is with WMB's configstore tables.
1. Stop the broker.
mqsistop <BrokerName>
Where <BrokerName> is the name of your broker.
2. Enable broker agent trace.
mqsichangetrace <BrokerName> -t -b -l debug -c <file size in KB>
3. Enable the Execution Group startup trace.
mqsichangetrace <BrokerName> -t -e <EGName> -l debug -c <file size in KB>
Where <BrokerName> is the name of your broker.
This command can be run even when broker / EG are in stopped state.
Note: If you are tracing a broker/Execution Group startup abend problem, then use the following commands:
mqsichangetrace <BrokerName> -t -b -l debug -c <file size in KB> -m temp
mqsichangetrace <BrokerName> -t -e <EGName> -l debug -c <file size in KB> -m temp
4. Start the broker to recreate the problem.
5. Turn off trace
mqsichangetrace <BrokerName> -t -b -l none
mqsichangetrace <BrokerName> -t -e <EGName> -l none
6. Retrieve the trace log for specified component.
mqsireadlog <BrokerName> -t -b agent -f -o agent.xml
mqsireadlog <BrokerName> -t -e <EGName> -f -o <EGname>.xml
7. Format the XML log file
mqsiformatlog -i agent.xml -o agent.txt
mqsiformatlog -i <EGName>.xml -o <EGName>.txt
8. After a PMR is open, submit the files agent.txt and <EGName>.txt to IBM Support.
1. Stop the broker.
mqsistop <BrokerName>
Where <BrokerName> is the name of your broker.
2. Enable broker agent trace.
mqsiservice <BrokerName> -r Trace=debug
mqsiservice <BrokerName> -r TraceSize=6291453
3. Enable execution group trace.
mqsiservice <BrokerName> -r executionGroupTraceOverrideLevel=debug
Note: This command should be input on a single line.
mqsiservice <BrokerName> -r executionGroupTraceOverrideSize=100000000
Note: This command should be input on a single line.
4. Start the broker.
mqsistart <BrokerName>
5. Recreate the problem (check for errors in the syslog or event viewer log).
6. Stop the broker. Make sure the broker is stopped.
mqsistop <BrokerName>
7. Retrieve the trace log for specified component.
mqsireadlog <BrokerName> -t -b agent -f -o agent.xml
mqsireadlog <BrokerName> -t -e <EGName> -f -o <EGName>.xml
Where <EGName> is the name of your execution group.
8. Format the XML log file.
mqsiformatlog -i agent.xml -o agent.txt
mqsiformatlog -i <EGName>.xml -o <EGName>.txt
9. Turn off trace.
mqsiservice <BrokerName> -r Trace=""
mqsiservice <BrokerName> -r TraceSize=""
mqsiservice <BrokerName> -r executionGroupTraceOverrideLevel=""
mqsiservice <BrokerName> -r executionGroupTraceOverrideSize=""
10. After a PMR is open, submit the files agent.txt and <EGName>.txt to IBM Support.
Product Alias/Synonym
WMB MB WebSphere Message Broker MQ Integrator WBIMB WBI-MB MQSI WMQI
Rate this page:
Copyright and trademark information
IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.