| Author |
Message
|
| LMarshall |
 Posted: Fri Jun 09, 2006 3:49 am Post subject: Problem with User Trace |
 |
|
Newbie
Joined: 09 Jun 2006
Posts: 4
|
Hi All,
I hope someone can help with an issue I have when running a user trace.
I have deployed a message flow and a message set and they execute successfully. However when I execute mqsireadlog to retrieve the user trace information it just hangs. I get some errors my event viewer...
... An internal software error has occurred in the message broker. Further messages will indicate the effect of this error on the broker's transactions. The diagnostic information associated with this message is: '
Severe Abend Error detected.
....
I am running locally on Windows XP with Message Broker 6.0.
Thanks,
L |
|
| Back to top |
|
 |
| wschutz |
| Posted: Fri Jun 09, 2006 5:13 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
My first suggestion in cases like this is always to put the latest service on the broker. 
_________________
-wayne |
|
| Back to top |
|
|
| JT |
| Posted: Fri Jun 09, 2006 6:55 am Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
Try issuing the '-r' option on the mqsichangetrace command to discard previous trace entries. Then re-issue the mqsireadlog command.
By the way, what's the format of the mqsireadlog command you're using. |
|
| Back to top |
|
|
| LMarshall |
| Posted: Fri Jun 09, 2006 6:56 am Post subject: |
|
|
Newbie
Joined: 09 Jun 2006
Posts: 4
|
I've finally gotten some feedback from the user trace...
It seems that there is a parseing error in the when reading the trace file. Anyone come across this before? It seems i on;y get this issue with larger messages.
BIP8036E: Negative response received. This command sends an internal configuration message to the broker, the response received indicated that the internal configuration message was unsuccessful. Check that the WebSphere MQ transport is available. Check the system log for further information.
BIP5004E: XML parsing error ('Invalid document structure ') encountered on line 1 column 40 while parsing element ''. The above error was reported by the generic XML parser. This message is usually caused by a badly-formed XML message. Check that the XML message being passed in is a well-formed XML message that adheres to the XML specification. Note that the line number and column number quoted above give the p
osition where the parser discovered the problem. The actual error may be earlier in the message. Internal error codes : (-1), ('').
BIP8047E: Unable to parse the data received, exception caught 'ImbException'. The command uses parser functions to analyze XML data, the parser has detected a in error in the format of the XML data being parsed. Use the line number and column number to locate the XML causing the problem. Check that the data being parsed is correctly formatted. The command may produce partial output. It may also be possible to modify the XML data that the command is parsing so that the error does not occur. |
|
| Back to top |
|
|
| LMarshall |
| Posted: Fri Jun 09, 2006 7:00 am Post subject: |
|
|
Newbie
Joined: 09 Jun 2006
Posts: 4
|
I have installed the latest service on the broker - CSD1
I am also using the -r option with the mqsichangetrace.
 |
|
| Back to top |
|
|
| JT |
| Posted: Fri Jun 09, 2006 7:03 am Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
| Post the syntax of the commands you're using. |
|
| Back to top |
|
|
| LMarshall |
| Posted: Fri Jun 09, 2006 7:08 am Post subject: |
|
|
Newbie
Joined: 09 Jun 2006
Posts: 4
|
Here's the sytax I'm using.....
mqsichangetrace BrokerName -u -e default -r -l debug -c 2000000
mqsireadlog BrokerName -u -e default -o output.xml
mqsiformatlog -i output.xml -o output.log |
|
| Back to top |
|
|
| JT |
| Posted: Fri Jun 09, 2006 7:20 am Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
| I noticed that we use the '-f' flag on the mqsireadlog command, as does the IA0R - Reformat User Trace Utility supportpac. |
|
| Back to top |
|
|
|
|
