| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Questions regarding monitoring events |
« View previous topic :: View next topic » |
| Author |
Message
|
| ashetty |
 Posted: Mon Apr 28, 2014 6:18 am Post subject: Questions regarding monitoring events |
 |
|
Newbie
Joined: 17 Oct 2013
Posts: 3
|
Hello,
[MB v8.0.0.2]
I have a message flow as follows:
MQInputNode---->ComputeNode------->MQOutputNode
Catch and Failure terminals of MQInputNode are connected to a Throw node.
In the MQInputNode, I have configured Transaction Start, Transaction End, Catch Terminal and Failure Terminal events.
For a successful scenario, I am getting TransactionStart and TransactionEnd events which is as expected.
But whenever a excpetion occurs beyond MQInputNode (say User Exception in Compute Node) following events are being emitted.
1.Transaction Start Event
2.Catch Terminal Event [Exception List has proper exception regarding why the message has failed]
3.Transaction Start Event
4.Failure Terminal Event[Exception List says "Dequeued Failed Message.Propagating a message to failure terminal"]
5.Transaction Start Event
6.Transaction End Event
My questions are,
1. Why am I getting three 'Transaction Start' events for a single input message?
2.Why there is a 'Transaction End' event even when my input message has failed?
3.Why a 'Failure Terminal Event' is generated with 'Dequeued Failed Message' error?
Please let me know your thoughts, suggestionsor any links that will answer these.
Thanks |
|
| Back to top |
|
 |
| Esa |
| Posted: Mon Apr 28, 2014 6:50 am Post subject: Re: Questions regarding monitoring events |
|
|
Grand Master
Joined: 22 May 2008
Posts: 1387
Location: Finland
|
| ashetty wrote: |
1. Why am I getting three 'Transaction Start' events for a single input message? |
You should really capture "Transaction Rollback" events, too. That would make it more clear to you.
The first transaction ends with rollback when the catch terminal Throw node fires. No "Transaction End" event, but a "Transaction Rollback" that you don't capture.
The second transaction happens when the flow reads the message again, detects that the backout count of the message is bigger than the backout treshold of the input queue. Message is propagated to failure, an exception is thrown because you put a Throw node there. No "Transaction End" event (but a Rollback that you don't capture). The message is backed out again, because of the rollback.
The third transaction is when the flow reads the message again, detects that the backout cound exceeds the backout treshold with more than one and puts the message in the backout queue or the qm's DLQ. A Transaction End event is emitted.
| ashetty wrote: |
| 3.Why a 'Failure Terminal Event' is generated with 'Dequeued Failed Message' error? |
That is the exception that you always get when MQ Input propagates to failure terminal after the main flow has thrown and exception and the message has been backed out. |
|
| 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
|
|
|
|
