| Author |
Message
|
| giorginus80 |
 Posted: Tue Apr 14, 2009 5:07 am Post subject: AggregateReply get Dequeued failed message |
 |
|
Centurion
Joined: 08 Jul 2008
Posts: 124
Location: Rome, Italy
|
Hi,
I have a flow with Aggregation. If I have a big message I have problems, this not happen with medium message. I don't have a specific exception but
| Code: |
( ['MQROOT' : 0x8dd3970]
(0x01000000:Name):RecoverableException = (
(0x03000000:NameValue):File = '/build/S610_P/src/DataFlowEngine/ImbMqInputNode.cpp' (CHARACTER)
(0x03000000:NameValue):Line = 1992 (INTEGER)
(0x03000000:NameValue):Function = 'ImbCommonInputNode::eligibleForBackout' (CHARACTER)
(0x03000000:NameValue):Type = 'ComIbmMQInputNode' (CHARACTER)
(0x03000000:NameValue):Name = 'AggrReplyIn#FCMComposite_1_3' (CHARACTER)
(0x03000000:NameValue):Label = 'AggrReplyIn.InputReply' (CHARACTER)
(0x03000000:NameValue):Catalog = 'BIPv610' (CHARACTER)
(0x03000000:NameValue):Severity = 3 (INTEGER)
(0x03000000:NameValue):Number = 2652 (INTEGER)
(0x03000000:NameValue):Text = 'Dequeued failed message. Propagating a message to the failure terminal' (CHARACTER)
)
)
|
I have this on the AggregateReply Node, and the crazy things is that sometime give me the error, sometimes no, with the same big message. |
|
| Back to top |
|
 |
| WMBDEV1 |
| Posted: Tue Apr 14, 2009 5:40 am Post subject: Re: AggregateReply get Dequeued failed message |
|
|
Sentinel
Joined: 05 Mar 2009
Posts: 888
Location: UK
|
| giorginus80 wrote: |
Hi,
I don't have a specific exception but
|
Why not?
A user trace may be helpful here and maybe we can help you with a specific answer! |
|
| Back to top |
|
|
| giorginus80 |
| Posted: Tue Apr 14, 2009 5:42 am Post subject: Re: AggregateReply get Dequeued failed message |
|
|
Centurion
Joined: 08 Jul 2008
Posts: 124
Location: Rome, Italy
|
| WMBDEV1 wrote: |
A user trace may be helpful here and maybe we can help you with a specific answer! |
Really, I have a trace node, and the Exception it's only this. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Apr 14, 2009 9:15 am Post subject: Re: AggregateReply get Dequeued failed message |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| giorginus80 wrote: |
| WMBDEV1 wrote: |
A user trace may be helpful here and maybe we can help you with a specific answer! |
Really, I have a trace node, and the Exception it's only this. |
A trace node is only related to a user trace if you tell the user trace to log itself to the user trace, rather than to a file. |
|
| Back to top |
|
|
| giorginus80 |
| Posted: Wed Apr 15, 2009 12:59 am Post subject: Re: AggregateReply get Dequeued failed message |
|
|
Centurion
Joined: 08 Jul 2008
Posts: 124
Location: Rome, Italy
|
| mqjeff wrote: |
| giorginus80 wrote: |
| WMBDEV1 wrote: |
A user trace may be helpful here and maybe we can help you with a specific answer! |
Really, I have a trace node, and the Exception it's only this. |
A trace node is only related to a user trace if you tell the user trace to log itself to the user trace, rather than to a file. |
Then how can I read the exception in the user trace, related to the last operation? |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Apr 15, 2009 1:20 am Post subject: Re: AggregateReply get Dequeued failed message |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| giorginus80 wrote: |
| Then how can I read the exception in the user trace, related to the last operation? |
By following the instructions in the documentation for taking a user trace (ideally at debug level) using mqsichangetrace, mqsireadlog and mqsiformat log. |
|
| Back to top |
|
|
| WMBDEV1 |
| Posted: Wed Apr 15, 2009 1:21 am Post subject: |
|
|
Sentinel
Joined: 05 Mar 2009
Posts: 888
Location: UK
|
Turn debug user trace on.....
put your message
| Code: |
mqsireadlog
mqsiformatlog |
turn trace off.....
Inspect the generated file for more clues than previsouly provided. |
|
| Back to top |
|
|
| WMBDEV1 |
| Posted: Wed Apr 15, 2009 1:22 am Post subject: |
|
|
Sentinel
Joined: 05 Mar 2009
Posts: 888
Location: UK
|
Drat, maybe if i hadnt formatted it nicely I would have beaten Jeff  |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Apr 15, 2009 1:30 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| WMBDEV1 wrote: |
| Drat, maybe if i hadnt formatted it nicely I would have beaten Jeff |
There's possibilities here for a whole thread on the virtues of speed v beauty...
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| giorginus80 |
| Posted: Wed Apr 15, 2009 2:10 am Post subject: |
|
|
Centurion
Joined: 08 Jul 2008
Posts: 124
Location: Rome, Italy
|
| WMBDEV1 wrote: |
Turn debug user trace on.....
put your message
| Code: |
mqsireadlog
mqsiformatlog |
turn trace off.....
Inspect the generated file for more clues than previsouly provided. |
After putting trace on, I had this:
| Code: |
2009-04-15 12:17:36.163635 31 UserTrace BIP6061I: Parser type ''XMLNSC'' created on behalf of node 'AggrReplyIn.InputReply' to handle portion of incoming message of length '1456' bytes beginning at offset '364'. Parser type selected based on value ''XMLNSC'' from previous parser.
2009-04-15 12:17:43.843032 1 Information BIP7407I: Publish/Subscribe subscriptions recovery started. Found ''10'' subscriptions.
The Publish/Subscribe broker is recovering subscriptions from the broker's database.
This message is for information only. There should be a matching message to indicate that recovery is complete; if such a message is not produced, then an error has occurred and it may be necessary to restart the broker.
2009-04-15 12:17:43.876785 1 Information BIP7410I: Publish/Subscribe subscriptions recovery. Recovered ''10'' subscriptions.
The Publish/Subscribe broker is recovering subscriptions from the broker's database.
This message is for information only. There should be a matching message to indicate that recovery is complete; if such a message is not produced, then an error has occurred and it may be necessary to restart the broker.
2009-04-15 12:17:43.876785 1 Information BIP7033I: Publish/Subscribe state recovery completed.
Recovery of the Publish/Subscribe state from the broker's database is complete.
This message is for information only. No action is required.
2009-04-15 12:17:54.017402 6 UserTrace BIP2631I: Backed out message being propagated to failure terminal; node 'AggrReplyIn.InputReply'.
Node 'AggrReplyIn.InputReply' has received a message which has previously been backed out because of a processing error in the message flow. The MQMD 'backoutCount' of the message exceeds (or equals) the 'backoutThreshold' defined for the WebSphere MQ input queue. The message broker is propagating the message to the failure terminal of the node.
Examine the other messages and the message flow to determine why the message is being backed out. Correct this situation if possible. Perform any local error recovery processing required.
2009-04-15 12:17:54.019321 6 UserTrace BIP6060I: Parser type ''Properties'' created on behalf of node 'AggrReplyIn.InputReply' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2009-04-15 12:17:54.020080 6 UserTrace BIP6061I: Parser type ''MQMD'' created on behalf of node 'AggrReplyIn.InputReply' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value ''MQHMD'' from previous parser.
2009-04-15 12:17:54.021305 6 UserTrace BIP6061I: Parser type ''XMLNSC'' created on behalf of node 'AggrReplyIn.InputReply' to handle portion of incoming message of length '1425' bytes beginning at offset '364'. Parser type selected based on value ''XMLNSC'' from previous parser.
2009-04-15 12:17:54.022079 6 UserTrace BIP2539I: Node 'AggrReplyIn.trace.Traccia': Evaluating expression ''ExceptionList'' at ('', '1.3'). This resolved to ''ExceptionList''. The result was ''ROW... Root Element Type=16777216 NameSpace='' Name='Root' Value=NULL''.
2009-04-15 12:17:54.022590 6 UserTrace BIP4067I: Message propagated to output terminal for trace node 'AggrReplyIn.trace.Traccia'.
The trace node 'AggrReplyIn.trace.Traccia' has received a message and is propagating it to any nodes connected to its output terminal.
No user action required.
|
I can't understand the error, because It can't explain me the real reason of the exception. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Apr 15, 2009 2:10 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| WMBDEV1 wrote: |
| Drat, maybe if i hadnt formatted it nicely I would have beaten Jeff |
Better men than you have tried...
| Vitor wrote: |
| There's possibilities here for a whole thread on the virtues of speed v beauty... |
...
No, I'm gonna leave that one alone. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Apr 15, 2009 2:21 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqjeff wrote: |
| WMBDEV1 wrote: |
| Drat, maybe if i hadnt formatted it nicely I would have beaten Jeff |
Better men than you have tried...
|
exerk has as well...
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Apr 15, 2009 2:29 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Do you have any .abend files?
It seems like the section of trace that you posted didn't cover the start of the error, just a portion of the error recovery.
You probably should open a PMR. |
|
| Back to top |
|
|
| giorginus80 |
| Posted: Wed Apr 15, 2009 2:37 am Post subject: |
|
|
Centurion
Joined: 08 Jul 2008
Posts: 124
Location: Rome, Italy
|
| mqjeff wrote: |
Do you have any .abend files?
It seems like the section of trace that you posted didn't cover the start of the error, just a portion of the error recovery.
You probably should open a PMR. |
No I haven't but in the trace I read
| Code: |
2009-04-15 12:17:54.017402 6 UserTrace BIP2631I: Backed out message being propagated to failure terminal; node 'AggrReplyIn.InputReply'.
Node 'AggrReplyIn.InputReply' has received a message which has previously been backed out because of a processing error in the message flow. The MQMD 'backoutCount' of the message exceeds (or equals) the 'backoutThreshold' defined for the WebSphere MQ input queue. The message broker is propagating the message to the failure terminal of the node.
Examine the other messages and the message flow to determine why the message is being backed out. Correct this situation if possible. Perform any local error recovery processing required.
|
So I increased the Backout Threeshold in the Input Queue and now I have no error. So it seems that in the MQMD the backout property is greater than input queue property, so It got an error, but I don't know why the MQMD backout property is greater. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Apr 15, 2009 2:42 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| giorginus80 wrote: |
| So I increased the Backout Threeshold in the Input Queue and now I have no error. So it seems that in the MQMD the backout property is greater than input queue property, so It got an error, but I don't know why the MQMD backout property is greater. |
The only reason the MQMD backout count gets incremented is because a message causes an error and then gets backed out.
By increasing the backout count, you're increasing the number of times it will try to do the same thing before it fails entirely.
But you still haven't figured out why it fails in the first place...
I think there's more information in the usertrace about that, somewhere. |
|
| Back to top |
|
|
|
|
