|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
What is BackoutRequeueQName?????? |
« View previous topic :: View next topic » |
Author |
Message
|
eswarnv |
Posted: Sat Dec 21, 2002 2:06 am Post subject: What is BackoutRequeueQName?????? |
|
|
Voyager
Joined: 20 Dec 2001 Posts: 88
|
Hi
Can any body give Idea abt what is the significance of BackoutRequeueQName, BackoutThreshold and hardened back out attributes of a Queue??
I have gone thru Application Reference Guide, But I failed to understand.
Thanks in Advance
Eswar. |
|
Back to top |
|
 |
bob_buxton |
Posted: Sat Dec 21, 2002 2:07 pm Post subject: |
|
|
 Master
Joined: 23 Aug 2001 Posts: 266 Location: England
|
If an application fails to process a message and backs out the message will be returned to the queue and the application will get it again.
If the original problem was a temporary failure it may be OK this time but if it fails again an endless loop may develop.
The backout count is the number of times the message has failed.
The backout threshold is an indication to the application how many times it should attempt to retry processing the message before writing it to the requeue queue.
Note it is up to the application to move the message (if it wants to) the queue manager does not check the threshold.
To maintain the backout count across a queue manager restart requires extra work and IO so impacts performance and therefore is optional. _________________ Bob Buxton
Ex-Websphere MQ Development |
|
Back to top |
|
 |
eswarnv |
Posted: Sat Dec 21, 2002 7:53 pm Post subject: |
|
|
Voyager
Joined: 20 Dec 2001 Posts: 88
|
|
Back to top |
|
 |
bower5932 |
Posted: Mon Dec 23, 2002 9:23 am Post subject: |
|
|
 Jedi Knight
Joined: 27 Aug 2001 Posts: 3023 Location: Dallas, TX, USA
|
|
Back to top |
|
 |
kingdon |
Posted: Mon Dec 23, 2002 11:59 pm Post subject: |
|
|
Acolyte
Joined: 14 Jan 2002 Posts: 63 Location: UK
|
There's also an MQJMS specific slant. The JMS layer will attempt to use the backout queue name and backout threshold settings to redirect messages that cause multiple failures when using asynchronous message delivery, i.e. if the onMessage method terminates by throwing a RuntimeException. However, throwing RuntimeExceptions from onMessage is discouraged, and relying on this MQ specific behaviour will reduce portability.
Regards,
James. |
|
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
|
|
|
|