| Author |
Message
|
| pratuluv |
 Posted: Wed Oct 12, 2011 3:58 am Post subject: Failure Terminal |
 |
|
Acolyte
Joined: 25 May 2011
Posts: 53
|
Hi, What will happen if the Failure terminal of a MQInput Node is not connected and only Catch terminal is connected? I have read through the Help guide on the topics related to this.
But I need some more clarity.
I presume that if any failure occurs, then, since the failure is not connected, the control will come to the catch terminal.
But I am not sure if all the scenarios will be taken care by the catch terminal. Is there any specific reason why we have to connect the failure terminal also? |
|
| Back to top |
|
 |
| exerk |
| Posted: Wed Oct 12, 2011 4:16 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Moving this to the Broker forum, where it belongs...
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Wed Oct 12, 2011 4:21 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
If any terminal is unconnected, the events that would have been propagated on that terminal will be lost. I'm not sure why you don't have clarity on this topic, unless you did not take the IBM-provided training for Broker developers.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| pratuluv |
| Posted: Wed Oct 12, 2011 4:43 am Post subject: Failure Terminal |
|
|
Acolyte
Joined: 25 May 2011
Posts: 53
|
Hi,
If any terminal is unconnected, the events that would have been propagated on that terminal will be lost. I'm not sure why you don't have clarity on this topic, unless you did not take the IBM-provided training for Broker developers.
To answer your above reply, If the failure terminal is not connected, the message will be propogated automatically to the Catch terminal. The message will not be lost. I just want to be sure that connecting the catch terminal alone is sufficient.
Looks like you have been very well trained by IBM, so it would be of great help if you can enlighten me as well with some of your knowledge  |
|
| Back to top |
|
|
| MrSmith |
| Posted: Wed Oct 12, 2011 5:14 am Post subject: |
|
|
Master
Joined: 20 Mar 2008
Posts: 215
|
There are different factors to this depending on what your flow is configured with, in that you may have backout queues configured on the flow input queue etc etc, but in brief - there is a great functon on the toolkit called the help - this utility is great as it has the provision for searching for topics on which your interested - i briefly just offhand tried Handling MQInput errors using this marvellous tool and bless me found exactly what i was looking for in the simplest of terms. If having read that you still do not understand then you should repost.
lancelotlinc is correct in that the broker course labours this point as a major part of Error handling.
HTH
_________________
-------- *
“Outside of a dog, a book is man's best friend. Inside of a dog it's too dark to read.” |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Wed Oct 12, 2011 5:24 am Post subject: Re: Failure Terminal |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| pratuluv wrote: |
Hi,
If any terminal is unconnected, the events that would have been propagated on that terminal will be lost. I'm not sure why you don't have clarity on this topic, unless you did not take the IBM-provided training for Broker developers.
To answer your above reply, If the failure terminal is not connected, the message will be propogated automatically to the Catch terminal. The message will not be lost. I just want to be sure that connecting the catch terminal alone is sufficient.
Looks like you have been very well trained by IBM, so it would be of great help if you can enlighten me as well with some of your knowledge |
Are you needing supervision to use Google?
This Google-found quote from a document may help clarify, but again I do not know why you need clarification.
| Quote: |
In general, if a path is not defined for a failure (that is, neither the Catch terminal nor the Failure terminal of the MQInput node is connected):
■Non-transactional messages are discarded.
■Transactional messages are rolled back to the input queue to be tried again:
■If the backout count of the message is less than the backout threshold (BOTHRESH) of the input queue, the message is tried again and sent to the Out terminal.
■When the backout count equals or exceeds the backout threshold, one of the following might happen:
■The message is placed on the backout queue, if one is specified (using the BOQNAME attribute of the input queue.)
■The message is placed on the dead-letter queue, if there is no backout queue defined or if the MQPUT to the backout queue fails.
■If the MQPUT to the dead-letter queue fails, or if there is no dead-letter queue defined, then the message flow loops continuously trying to put the message to the dead-letter queue.
■If a path is defined for the failure, then that path defines the destination of the message. If both the Catch terminal and the Failure terminal are connected, the message is propagated through the Catch terminal.
|
Have you taken the WM663 class? If not, why not?
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| rekarm01 |
| Posted: Thu Oct 13, 2011 1:42 am Post subject: Re: Failure Terminal |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 1415
|
| lancelotlinc wrote: |
| If any terminal is unconnected, the events that would have been propagated on that terminal will be lost. |
But that's not true for Failure terminals ... which is what the OP asked about.
| lancelotlinc wrote: |
| Are you needing supervision to use Google? |
Anybody can Google an irrelevant quote from a random document, and post it. For example:
| lancelotlinc wrote: |
This Google-found quote from a document may help ...
| Quote: |
| In general, if a path is not defined for a failure (that is, neither the Catch terminal nor the Failure terminal of the MQInput node is connected): ... |
|
But that quote doesn't explain what happens if the Catch terminal is connected ... which is what the OP asked about.
| lancelotlinc wrote: |
| I'm not sure why you don't have clarity on this topic ... |
lancelotlinc might do well to examine his own lack of clarity on this topic, before berating anyone else for theirs. |
|
| Back to top |
|
|
| rekarm01 |
| Posted: Thu Oct 13, 2011 1:43 am Post subject: Re: Failure Terminal |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 1415
|
| pratuluv wrote: |
| If the failure terminal is not connected, the message will be propogated automatically to the Catch terminal. |
No, it won't:- The MQInput.Catch flow generally handles Exceptions thrown from the MQInput.Out flow.
- The MQInput.Failure flow generally handles internal errors from the MQInput node itself.
The WMB v7 Info Center explains this in greater detail, here, here, here, here, and here.
The WMB v6 Info Center also describes non-transactional error handling here, but that explanation does not appear in later versions. |
|
| Back to top |
|
|
| pratuluv |
| Posted: Mon Oct 17, 2011 8:08 pm Post subject: Failure terminal |
|
|
Acolyte
Joined: 25 May 2011
Posts: 53
|
| Thanks for your replies. The links provided by "rekarm01" were very useful. I will do a POC for further analysis. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Oct 18, 2011 2:19 am Post subject: Re: Failure terminal |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| pratuluv wrote: |
| Thanks for your replies. The links provided by "rekarm01" were very useful. I will do a POC for further analysis. |
 |
|
| Back to top |
|
|
|
|
