| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| WBIMB (V5) Debugger Can Affect Outcome (?) |
« View previous topic :: View next topic » |
| Author |
Message
|
| Ching |
 Posted: Fri Apr 13, 2007 2:23 pm Post subject: WBIMB (V5) Debugger Can Affect Outcome (?) |
 |
|
Apprentice
Joined: 08 Nov 2004
Posts: 25
Location: Portland, OR
|
Hey everyone,
I'm debugging a message flow, and I noticed that when using the debugger, the outcome is different than when not using the debugger.
The input data is exactly the same for both cases. I'm using MQ Visual Edit to 'restore' the message to the input queue.
For the case when I'm not using the debugger, there is an exception, and the data is rolled back.
BIP5181:
Message
Custom Wire Format error. Message bitstream smaller than expected.
Current element '<insert_0>'.
Explanation
The bitstream is smaller than expected for a CWF message of this message type. Check that the input message is correctly structured, and has not been corrupted. Check the MRM definition of this message type.
See following messages for more details.
For the case when using the debugger, the data does not roll back.
I'm just curious if anyone has seen this type of behavior. What is the debugger doing that causes the result to be different?
I appreciate any comments.
Ching |
|
| Back to top |
|
 |
| gbbailey |
| Posted: Mon Apr 16, 2007 12:56 am Post subject: |
|
|
Apprentice
Joined: 12 May 2006
Posts: 27
Location: London, UK
|
| The debugger is parsing the message at a different point in the flow to where you are getting that (parsing) error message. |
|
| 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
|
|
|
|
