| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Backout logic behind backout queue for MQ-Triggered Txn |
« View previous topic :: View next topic » |
| Author |
Message
|
| sumansengupta07 |
 Posted: Thu Oct 30, 2014 9:49 pm Post subject: Backout logic behind backout queue for MQ-Triggered Txn |
 |
|
Novice
Joined: 14 Nov 2013
Posts: 23
|
Could anyone please let me know whether application code contains any backout logic for the backout queue?
As per my knowledge when the backout count exceeds the backout threshold, the MQ Queue Manager object moves the poison message to the backout queue. It happens because we manually map the local request queue with the backout queue with backout threshold. So I don't think any backout logic needs to be defined in the corresponding application program for the backout queue.
 |
|
| Back to top |
|
 |
| MQsysprog |
| Posted: Fri Oct 31, 2014 12:13 am Post subject: |
|
|
Centurion
Joined: 24 Feb 2014
Posts: 116
|
Hello,
The backout queue is a mechanism designed to assist the application programmer when dealing with poisoned messages ,or speaking in other way to examine and analyse the data contained in these messages in order to detect the reason of handling failure, by your application logic .
Then you can correct the data in the payload of these messages ,and requeue them to the relevant application queues ,for the appropriate
reprocessing . |
|
| Back to top |
|
|
| zpat |
| Posted: Fri Oct 31, 2014 12:18 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
MQ does not move the messages. The application has to inspect the backout count of each message and move it when appropriate.
The queue attributes are just a place to store the values for reference.
Whether your application (CICS or whatever) has some logic to do this is something I don't know. WMB has such logic.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Oct 31, 2014 5:07 am Post subject: Re: Backout logic behind backout queue for MQ-Triggered Txn |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| sumansengupta07 wrote: |
| As per my knowledge when the backout count exceeds the backout threshold, the MQ Queue Manager object moves the poison message to the backout queue. |
Your knowledge is wrong. The queue manager records the backout attributes but doesn't act on them. It's the responsibility of the application to honour them. WMB/IIB does this in it's guise as a well-behaved WMQ application, WAS does this on behalf of the WMQ applications running inside it's container and other similar containers may do as well.
To the best of my knowledge, CICS doesn't do this but my knowledge may be as flawed as yours. A simple experiment will show you if it does or it doesn't. I'm assuming CICS as you've posted in the Mainframe section....
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| 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
|
|
|
|
