| Author |
Message
|
| tsuru |
 Posted: Fri Jul 28, 2006 10:58 am Post subject: Dequeued failed message |
 |
|
Novice
Joined: 25 Nov 2005
Posts: 24
Location: São Paulo
|
Hello there
Some of my messages are getting lost when put into my message flows.
Opening the trace node files I see:
"Dequeued failed message. Propagating a message to the failure terminal"
Can anyone help me? I could´t get anything on debug...
Does anyone knows what are the possible reasons for that?
thanks in advance! |
|
| Back to top |
|
 |
| Anirud |
| Posted: Fri Jul 28, 2006 11:03 am Post subject: Re: Dequeued failed message |
|
|
Master
Joined: 12 Feb 2004
Posts: 285
Location: Vermont
|
| tsuru wrote: |
"Dequeued failed message. Propagating a message to the failure terminal"
|
Doesn't this mean that the message is written to the Fail queue?
I believe, your message is not lost, but it is written to the Fail queue (if you have one).
You need to give us more information. |
|
| Back to top |
|
|
| wbi_telecom |
| Posted: Fri Jul 28, 2006 11:13 am Post subject: |
|
|
Disciple
Joined: 15 Feb 2006
Posts: 188
Location: Harrisburg, PA
|
| Is the failure terminal of the input node connected ? Connecting it to a trace node and using pattern ${ExceptionList} should give you the exception details because of which the messages are going to failure. |
|
| Back to top |
|
|
| tsuru |
| Posted: Fri Jul 28, 2006 11:13 am Post subject: |
|
|
Novice
Joined: 25 Nov 2005
Posts: 24
Location: São Paulo
|
Thanks, Anirud.
Here is the exception message:
Exception:
---------
(
(0x01000000):RecoverableException = (
(0x03000000):File = '/build/S500_P/src/DataFlowEngine/ImbMqInputNode.cpp'
(0x03000000):Line = 3270
(0x03000000):Function = 'ImbMqInputNode::eligibleForBackout'
(0x03000000):Type = 'ComIbmMQInputNode'
(0x03000000):Name = '#FCMComposite_1_1'
(0x03000000):Label = 'com.vr.capturapedidos.kitvr.EAI_KitVR.IN'
(0x03000000):Text = 'Dequeued failed message. Propagating a message to the failure terminal'
(0x03000000):Catalog = 'BIPv500'
(0x03000000):Severity = 3
(0x03000000):Number = 2652
)
)
In the flow, the MQInput terminals are all connected. Failure and catch connectors are connected to MQOutput node, which is the fail queue. |
|
| Back to top |
|
|
| wbi_telecom |
| Posted: Fri Jul 28, 2006 11:21 am Post subject: |
|
|
Disciple
Joined: 15 Feb 2006
Posts: 188
Location: Harrisburg, PA
|
| Can you give us some more details about what the message flow is trying to do and where exactly the message is failing? |
|
| Back to top |
|
|
| tsuru |
| Posted: Fri Jul 28, 2006 11:39 am Post subject: |
|
|
Novice
Joined: 25 Nov 2005
Posts: 24
Location: São Paulo
|
Sure.
The message flow does the following things:
1) Message enter as BLOB
2) MQInput out terminal is connected to a Compute Node which parses the incoming message to MRM domain.
3) There is a following Compute Node which does a business validation of the message. If there are business errors, then I do PROPAGATE to 2 queues. Else the flow end.
The MQInput catch terminal enter into Compute Node that put the failing message to fail queue. The MQInput failure terminal does the same. |
|
| Back to top |
|
|
| Anirud |
| Posted: Fri Jul 28, 2006 1:24 pm Post subject: |
|
|
Master
Joined: 12 Feb 2004
Posts: 285
Location: Vermont
|
| Please check the queue configuration (queue specified in the output node). Is it configured? |
|
| Back to top |
|
|
| moogoo |
| Posted: Sun Jul 30, 2006 8:30 pm Post subject: |
|
|
Acolyte
Joined: 20 Sep 2002
Posts: 54
Location: US
|
Also, I've found it helpful to connect a trace node to the failure or catch terminals of the MQOutput node. It should give a clearer description of why its bombing out before rolling the message all the way back to the MQInput node.
MG |
|
| Back to top |
|
|
| Nizam |
| Posted: Thu Aug 24, 2006 2:29 pm Post subject: |
|
|
Disciple
Joined: 10 Feb 2004
Posts: 160
|
|
| Back to top |
|
|
| dilse |
| Posted: Fri Aug 25, 2006 1:00 pm Post subject: |
|
|
Master
Joined: 24 Jun 2004
Posts: 270
|
tsuru,
As I see the error information, it is evident that the message failed in/After compute node or it may be failed on the MQInput node itself. Check the following:
1. Make sure you have selected the Message Domain as 'BLOB' on MQInput node.
2. Did you connect failure, Catch terminals of MQInput nodes to any exception handlers or Queues?
3. Did you define your MQInput Queue to have a Requeue Queue to put the backout messages?
4. Is it reaching a compute nodw when you debug the message flow?
Debug the message flow using break points or trace log and let us know the behavious as to how it is flowing thru the message flow when you started debugging.
With the information you provided it is hard to analyze the situation but I am guessing your flow trying to write to a failed messsage to a Requeue Queue and failed to do it so it propagated the message to Failure terminal.
If you need help, you have got to make your problem clear.
DilSe..
_________________
DilSe..
Take life as it comes.. |
|
| Back to top |
|
|
| satyshh |
| Posted: Tue Jan 10, 2012 3:11 am Post subject: Dequeued failed message. Propagating a message to the failur |
|
|
Newbie
Joined: 18 Nov 2008
Posts: 6
|
Hi All,
we have faced the same issue(Dequeued failed message. Propagating a message to the failure terminal) and we found that there is a infinate loop in the code so we fixed that and it is working fine now.  |
|
| Back to top |
|
|
| NAIDU |
| Posted: Mon Oct 02, 2017 9:11 am Post subject: |
|
|
Novice
Joined: 12 Jan 2016
Posts: 17
|
| How can i generate this error , Here I need to fix this kind of issue, can some advice on this |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Oct 02, 2017 9:39 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| NAIDU wrote: |
| How can i generate this error , Here I need to fix this kind of issue, can some advice on this |
The OP hasn't posted here for 3 years.
If you want help, don't reopen these ancient threads that refer to old versions of the software and may no longer be applicable. Open a new thread (with more detailed information that "this kind of issue" please) and refer to any old threads you think may be relevant.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
