| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Poison Message and Backout queue |
« View previous topic :: View next topic » |
| Author |
Message
|
| g4Prakash |
 Posted: Mon Jan 10, 2005 2:04 am Post subject: Poison Message and Backout queue |
 |
|
Apprentice
Joined: 17 Dec 2002
Posts: 25
Location: INDIA
|
Hi All,
AIX platform:
-----------------
IBM WebSphere Application Server Enterprise, 5.0.2
WebSphere MQ Server 5.3 CSD05
I have a local queue LQ.request that has backout queue defined as LQ.backout.request, with backout threshold as 3 and hardened.
I have also defined the backout queue LQ.backout.request
The Mximum Retries in the WAS Listener Port is set to 5.
Scenario 1
-------------
When a valid XML message arrives on LQ.request the MDB consumes it, processes it and sends back a reply to another queue.
Scenario 2
-------------
The MDB reads the XML message, parses it, finds that it is invalid, throws up an exception. I am using Container Managed transactions so my understanding is that this invalid message is backed out to the request queue and the MDB will again read ...creatin a poison message.
My question
--------------
Do I need to write code for the invalid message to be moved to the Backout queue or will the Queue Manager move it automatically as I have mentioned all attributes in the request queue.
The sample backout.java code that I saw moves the invalid message after the backout threshold is reached ...does this mean that the application needs to move the poison message and the Queue Manager is not capable of doing this on its own?
Your early comments on this topic are appreciated. Also please suggest which manual/red paper/redbook should I refer to gain a better understanding of poison messages, WAS listener port stopping issue.
Thanks in advance. |
|
| Back to top |
|
 |
| JLRowe |
| Posted: Mon Jan 10, 2005 5:33 am Post subject: |
|
|
Yatiri
Joined: 25 May 2002
Posts: 664
Location: South East London
|
The maximum retries on the WAS listener determines when the listener shuts down, the backout threshold on the queue determines when the message is placed on the backout queue.
In your setup, the message will be delivered 3 times to the MDB, and then MQ will place it on the backout queue.
If your maximum retries was less then your backout threshold, then the listener port would shut down. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Jan 10, 2005 1:03 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Remember the WAS MDB implementation is what moves the message to the relevant backout queue / DLQ if no backout queue is specified.
The qmgr does nothing of this by itself. It just increases the backout count by 1 every time the message is rolled back (exception raised) .
Enjoy  |
|
| 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
|
|
|
|
