MQSeries.net :: View topic - Need some help to understand a bad Message problem

WBI_user · Posted: Tue Oct 23, 2007 2:13 pm Post subject:

I am running WMB V6 CSD 5 on AIX, toolkit is on Windows XP , MQ is V6.02.1 on both AIX and WIN.

I have a bad nessage which seems to cause the flow to stop (I think). I need some help to understand my observation so that I can debug the problem.

I have a bad XML message (I think) from external client (about 5K in size)

The flow I used for testing is very simple
MQINPUT(IN.Q) - trace - compute - MQOUTPUT(OUT.Q)
Compute node is just copy entire message.
Both MQINPUT and Compute has the failure terminal connected to another MQOUTPUT node (FAIL.Q)
ALl nodes has transaction=no
MQINPUT has parse imediate and XMLNS domain
IN.Q has backout threshold=0 and BACKOUT.Q specified.

I use a good XML message tp test the flow. Message go to OUT.Q as expected. Curdepth of IN.Q goes to zero.

I then put the bad XML message to IN.Q. Curdepth of IN.Q remain at 1.
Queue status of IN.Q shows no uncommitted message, curdepth of 1 and the dataflow engine has the queue open for input.

The fact that the curdpeth of the IN.Q remain at 1 says
1. The flow is not picking the message OR
2. The flow has rolled the message back to the Input Q. This is not what I expect. I think if the INPUT node decided to roll the message back, it should go to the back out requeue queue specifed or the dead letter queue if the backout queue is not usable for whatever reason.
I check the backout count of the message on IN.Q, it is zero ????

I then put the bad message to IN.Q again. Now IN.Q has 2 messages. I think the flow must be stopped. But the toolkit shows no indication that the flow has stopped.

I then put a good XML message to IN.Q. It now has a curdepth of 3 which is expected.

Thinking the the flow may have stopped. I use the toolkit to stop and then start the message flow. This time, the good XML message was pciked up and show up on the output queue. The two bad XML message remains on IN.Q.

I need to find out what's wrong with the bad XML. But I do not understand why things are happening the way I described. I try to use debug, but the bad message do not even leave the MQINPUT node, so it does not stop at the first break point.

I ran MQSI trace, for the good XML message I can see

2007-10-23 10:56:27.759342 7721 UserTrace BIP6060I: Parser type ''Properties'' created on behalf of node 'GET.get' to handle portion of incoming message of length 0 bytes beginning at offset '0'. and the rest ....

But when I have the bad XML, it shows
2007-10-23 11:04:57.104927 6940 UserTrace BIP6060I: Parser type ''Properties'' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2007-10-23 11:04:57.104972 6940 UserTrace BIP6061I: Parser type ''MQMD'' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value ''MQHMD'' from previous parser.
2007-10-23 11:04:57.105087 6940 UserTrace BIP6061I: Parser type ''XMLS'' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '205' bytes beginning at offset '364'. Parser type selected based on value ''XMLS'' from previous parser.

and nothing else....

Any suggestion on how can I find out what's wrong with the bad XML message ?