| Author |
Message
|
| new_to_wmb8 |
 Posted: Thu Feb 19, 2015 3:39 am Post subject: Manually Increase backout Count |
 |
|
Centurion
Joined: 28 May 2013
Posts: 127
Location: Hyderabad, India
|
Hi All,
I have a requirement in which i have to manually increase the back out count to restrict the retry mechanism for soem scerios.
I am setting OutputRoot.MQMD.Backout = Max Value
But when the exception occur, its all reset to its actuall value.
Is there any other way to implement this?
Thanks |
|
| Back to top |
|
 |
| Esa |
| Posted: Thu Feb 19, 2015 5:17 am Post subject: |
|
|
Grand Master
Joined: 22 May 2008
Posts: 1387
Location: Finland
|
I don't think you can programmatically increase backout count. The only way to increase it is to back out the message.
So you need to modify the retry mechanism so that it ignores the message when it detects one of your scenarios.
Or revise the requirement. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Feb 19, 2015 5:59 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Esa wrote: |
I don't think you can programmatically increase backout count. The only way to increase it is to back out the message.
So you need to modify the retry mechanism so that it ignores the message when it detects one of your scenarios.
Or revise the requirement. |
Alternatively your flow can enquire about the backout count of the message and take a different action depending on the operation and value of the backout count. Like put the message on an error queue instead of rolling the message back... and you'd have to do it off the failure terminal so that you can roll back any other operations involved...
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| new_to_wmb8 |
| Posted: Thu Feb 19, 2015 6:15 am Post subject: |
|
|
Centurion
Joined: 28 May 2013
Posts: 127
Location: Hyderabad, India
|
Actually i have to maintain the Transaction of the flow and maintain the sequence .so i can't put the message in error queue.
Can you please suggest how we can ignore the message when one of the scenarios occur? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Feb 19, 2015 6:20 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| new_to_wmb8 wrote: |
Actually i have to maintain the Transaction of the flow and maintain the sequence .so i can't put the message in error queue.
Can you please suggest how we can ignore the message when one of the scenarios occur? |
Define ignore the message
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| new_to_wmb8 |
| Posted: Thu Feb 19, 2015 6:35 am Post subject: |
|
|
Centurion
Joined: 28 May 2013
Posts: 127
Location: Hyderabad, India
|
Got it!!!
Thanks for the suggestion.
Last edited by new_to_wmb8 on Thu Feb 19, 2015 7:07 am; edited 1 time in total |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Feb 19, 2015 7:02 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| new_to_wmb8 wrote: |
| can you please advice me how we can ignore the message. I am checking the headers MQMD and Properties and there is no way to simply ignore the message. |
You've been asked before what you mean by "ignore the message" and I ask again. Do you actually mean that when an error occurs you want to pretend the message was never sent? That's easy - push it to an unconnected terminal and you're good.....
Note also:
| new_to_wmb8 wrote: |
| i have to maintain the Transaction of the flow and maintain the sequence |
Messages which have to be processed in sequence are said to have "affinity" and it's a bad idea, for reasons you've discovered. Where a message is linked to it's predecessors or sucessors, you should use MQ grouping and logical sequencing.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Feb 19, 2015 7:04 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| new_to_wmb8 wrote: |
Thanks for the suggestion.
But can you please advice me how we can ignore the message. I am checking the headers MQMD and Properties and there is no way to simply ignore the message. |
What do you mean by "ignore"?
Do you mean "do not send further down stream?"
Then you basically mean delete.
Do you mean "delete"?
Simply don't propagate the message out of the node that determines the backout count is too high.
Do you mean "Process in an error condition"?
Do whatever that looks like, once you've determined the backout count is too high. |
|
| Back to top |
|
|
|
|
