| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Tracing messages with backout count > 0. |
« View previous topic :: View next topic » |
| Author |
Message
|
| Cogito-Ergo-Sum |
 Posted: Mon Sep 30, 2013 4:28 am Post subject: Tracing messages with backout count > 0. |
 |
|
Master
Joined: 07 Feb 2006
Posts: 293
Location: Bengaluru, India
|
I have a MQInput node reading from a message queue configured with a back-out queue (BOQ) with back-out count as 5. The MQInput node is wired to HTTPRequest node with a dummy URL which causes an exception.
This MQInput node has its Out terminal wired to a trace node set to ${Root}. I can see only the first pass; the subsequent ones (due to backout count setting) are not traced. However, the message does appear in the BOQ which means retry is happening. I was further able to confirm this by wiring the Failure terminal to another trace node. The trace output showed that had Backout count set was to 5.
There is this sentence in the Infocenter here:
| Quote: |
| You specify (or allow to default to zero(0)) the backout threshold attribute BOTHRESH when you create the queue. If you accept the default value of 0, the node increases this value to one (1). The node also sets the value to 1 if it cannot detect the current value. If the backout threshold is set to 1, the message is processed once but it is not retried through the Out terminal of the MQInput node. To retry the message at least once, set the backout threshold to 2. |
Does the italicized part mean, for higher backout count, the message with be processed through Out terminal ? If not, then how ? What if I wanted to take a different processing route based upon the backout count ?
_________________
ALL opinions are welcome.
-----------------------------
Debugging tip:When you have eliminated all which is impossible, then whatever remains, however improbable, must be the truth.
---Sherlock Holmes |
|
| Back to top |
|
 |
| McueMart |
| Posted: Mon Sep 30, 2013 4:47 am Post subject: |
|
|
Chevalier
Joined: 29 Nov 2011
Posts: 490
Location: UK...somewhere
|
Yes with a BOTHRESH of 5 specified, the message should be processed 5 times through the OUT terminal, and then the next time it is processed (i.e. when it's BOCOUNT is 5), it will go to the Failure terminal.
I am surprised if your trace nodes are not showing this behavior. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Mon Sep 30, 2013 4:48 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
I don't think you are reading your Trace node output correctly. Add CURRENT_GMTTIMESTAMP to you Trace node patterns. Make sure each Trace node points to a unique file on disk. Don't route more than one wire into a Trace node input.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| Cogito-Ergo-Sum |
| Posted: Mon Sep 30, 2013 10:43 pm Post subject: |
|
|
Master
Joined: 07 Feb 2006
Posts: 293
Location: Bengaluru, India
|
| McueMart wrote: |
| Yes with a BOTHRESH of 5 specified, the message should be processed 5 times through the OUT terminal, and then the next time it is processed (i.e. when it's BOCOUNT is 5), it will go to the Failure terminal. |
Thanks. That validates my understanding.
| McueMart wrote: |
| I am surprised if your trace nodes are not showing this behavior. |
Let me re-run the flow and see if I have missed something obvioud.
_________________
ALL opinions are welcome.
-----------------------------
Debugging tip:When you have eliminated all which is impossible, then whatever remains, however improbable, must be the truth.
---Sherlock Holmes |
|
| 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
|
|
|
|
