| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Poison message handling |
« View previous topic :: View next topic » |
| Author |
Message
|
| dwitherspoon |
 Posted: Tue Dec 09, 2003 5:59 am Post subject: Poison message handling |
 |
|
Acolyte
Joined: 09 Dec 2003
Posts: 59
|
Is JMS supposed to do poison message handling for me?
I was reading in http://www-3.ibm.com/software/integration/mqfamily/library/manualsa/csqzaw06/csqzaw066q.htm#Header_256 where it describes how when the backout threshold is reached the message gets moved to the configured backout queue.
Is JMS supposed to be doing that for my JMS client application? I have found some code that does backout processing of poison messages, but this really seems like code that would be in IBM's implemtation of JMS.
But what we're seeing is that a malformed message stays on the queue forever...it never gets backed out and moved off the queue.
_________________
Good...Fast...Cheap. Choose any two. |
|
| Back to top |
|
 |
| bower5932 |
| Posted: Tue Dec 09, 2003 6:59 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| The answer is that it depends. If you are doing simple (ie non-MDB) work, then the message doesn't get moved. However, if you have set up a ListenerPort, the message will get redelivered the backout number of times and then get moved to the backout queue. |
|
| Back to top |
|
|
| dwitherspoon |
| Posted: Tue Dec 09, 2003 7:28 am Post subject: |
|
|
Acolyte
Joined: 09 Dec 2003
Posts: 59
|
No, this is not a MessageDrivenBean application...I'm just using QueueConnection, QueueSession and a QueueReceiver. And I'm just doing a receive call when the exception occurs.
So do I need to handle moving malformed messages out of the way? If so, this kind of sucks. We want this to be a pure JMS application, but JMS cannot even receive the message to get it off of the queue, and that forces me to write MQI code to get rid of it.
Any ideas? Thanks much for your reply!!
_________________
Good...Fast...Cheap. Choose any two. |
|
| Back to top |
|
|
| dwitherspoon |
| Posted: Tue Dec 09, 2003 11:19 am Post subject: |
|
|
Acolyte
Joined: 09 Dec 2003
Posts: 59
|
Actually, this has gotten quite a bit contact admin. I have my JMS application, which uses a selector to pull messages of interest off the queue. When it hits a malformed message, I'd like to be able to move it to the backout queue. I have some code that takes the first message on the queue and moves that to the backout queue. But because I'm using a selector, I don't know which message it is that is causing the problem. It could be number 1, or it could be number 351.
And because JMS cannot even do the receive, I have no information about the message on the queue that is malformed...no message ID, no correlation ID, nothing I can use through the MQ base classes to locate and move that message.
Arrghh!
_________________
Good...Fast...Cheap. Choose any two. |
|
| Back to top |
|
|
| dwitherspoon |
| Posted: Wed Dec 31, 2003 7:27 am Post subject: IBM has accepted this a bug in their JMS Provider |
|
|
Acolyte
Joined: 09 Dec 2003
Posts: 59
|
Just for anybody following this one, I have successfully navigated the waters of IBM tech support, and they have accepted this as a bug in the JMS provider.  In short, if there is a problem with the header of a message, the JMS provider has to go through the backout processing configured for the queue. They agreed that it was unacceptable to leave the message on the queue with no way for the JMS client to clear or move the message (which it shouldn't have to do anyway).
Thanks to Ron for helping out with this one!
_________________
Good...Fast...Cheap. Choose any two. |
|
| 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
|
|
|
|
