|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Debugging an execution group that won't start ... |
« View previous topic :: View next topic » |
Author |
Message
|
kolban |
Posted: Wed Jan 15, 2003 5:41 am Post subject: Debugging an execution group that won't start ... |
|
|
 Grand Master
Joined: 22 May 2001 Posts: 1072 Location: Fort Worth, TX, USA
|
Folks,
Had a problem with starting an Execution Group. As soon as it started, it failed. As a result, I was unable to obtain a trace. IBM defect support gave me the following recipe which I thought I would log here:
Turn on EG startup tracing with the command:
mqsiservice <brokername> -r executionGroupTraceOverrideLevel=debug
Start the broker with:
mqsistart <brokername>
Deploy and as soon as the BIP2060 message appears in the syslog indicating that the execution group has terminated read the trace file with:
mqsireadlog <brokername> -t -e <execgroup> -f -o <execgroup>.xml
Format the trace file with :
mqsiformatlog -i <execgroup>.xml -o <execgroup>.txt |
|
Back to top |
|
 |
Yanghui |
Posted: Wed Jan 15, 2003 6:39 am Post subject: |
|
|
Disciple
Joined: 08 May 2002 Posts: 151 Location: Dublin, Ireland
|
Hi, Kolban,
Thanks for sharing this.
Since I can't find how to use the command mqsiservice in WMQI manual, do you know how to change the trave level back afterwards? Just setup as none or something else? What's the default setup? Many thanks.
Regards
-Yanghui |
|
Back to top |
|
 |
michaelpatton |
Posted: Tue Jan 28, 2003 5:32 pm Post subject: |
|
|
 Apprentice
Joined: 21 May 2002 Posts: 25 Location: East Coast USA
|
I believe to turn it off after you are done is:
mqsiservice <brokername> -r executionGroupTraceOverrideLevel=none |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|