| Author |
Message
|
| vairavan |
 Posted: Tue May 19, 2009 10:22 am Post subject: Message backed out to a queue |
 |
|
Apprentice
Joined: 22 Apr 2008
Posts: 42
|
Hi All,
Environment: MB V 6.1.0.3 and MQ 6.1
I have one schedular message flow puts a trigger(dummy) message(xml format) every 10 minutes to another message flow where I have one input queue (MQ Input node) Parser is XML parser.
This Flow doesn't expect the trigger message to be in any specified format. It just needs a trigger. And I have a compute node where I connect to database.
MQInput node --> Compute node --> MQOutput node
This flow worked fine for some days... And then on it started throwing this error message everytime, It receives message from Schedular.
I tried restarting the broker. What happens is... The time, I restart the broker, this flow picks up the message and then again goes to sleep mode. Messages from Schedular flow gets piled up and moves to backout queue.
Could any one give any thoughts on this?
Error Message:
----------------
BIP2648E: Message backed out to a queue; node 'MessageFlowName.InputQueueName'. : BrokerT6101_2.e9151164-1e01-0000-0080-a18ba665404a: /build/S610_P/src/DataFlowEngine/ImbMqInputNode.cpp: 2043: ImbCommonInputNode::eligibleForBackout: ComIbmMQInputNode: MessageFlowName#FCMComposite_1_1
Thanks... |
|
| Back to top |
|
 |
| WMBDEV1 |
| Posted: Tue May 19, 2009 10:33 am Post subject: |
|
|
Sentinel
Joined: 05 Mar 2009
Posts: 888
Location: UK
|
| Are you able to run a user trace when the message is being processed? This may give us more details to work with. |
|
| Back to top |
|
|
| vairavan |
| Posted: Tue May 19, 2009 5:43 pm Post subject: |
|
|
Apprentice
Joined: 22 Apr 2008
Posts: 42
|
Yes, It's going to Failure terminal. There the trace information says 'Dequeued the failed message, propagated to failure terminal'.
Not at all, going into the 'OUT' terminal of MQInput node. |
|
| Back to top |
|
|
| MQEnthu |
| Posted: Tue May 19, 2009 8:48 pm Post subject: |
|
|
Partisan
Joined: 06 Oct 2008
Posts: 329
Location: India
|
| vairavan wrote: |
| ....Parser is XML parser |
Don't use XML parser..It is depricated.. Use XMLNSC instead.
It appears that there must be some exception occuring in flow and message is being rolled back. Have you connected the catch and failure terminals of the MQInput node... Do you have any error handling processing? Check the flow why the message is being rolled back...
_________________
-----------------------------------------------
It is good to remember the past,
but don't let past capture your future |
|
| Back to top |
|
|
| vairavan |
| Posted: Wed May 20, 2009 9:10 am Post subject: |
|
|
Apprentice
Joined: 22 Apr 2008
Posts: 42
|
Problem got fixed. Thanks for your concern.
Actually the problem is. I have a database interation through a package call from Compute node. So Once the call made, it gets hung in the package, So, it never turned back.
So that's the problem. It's not with the parser, I use. I can use any parser there as I just expecting a junk message, which is going to be a trigger message.
Thanks for your help. |
|
| Back to top |
|
|
| WMBDEV1 |
| Posted: Wed May 20, 2009 9:16 am Post subject: |
|
|
Sentinel
Joined: 05 Mar 2009
Posts: 888
Location: UK
|
The note about the parser was cited as being a good thing to do (as the one you are using is deprecated), it was not cited as the root cause of your issue.
Good to hear you got it working though. |
|
| Back to top |
|
|
|
|
