Posted: Mon Aug 27, 2007 7:53 am Post subject: MDB and Backout
Apprentice
Joined: 02 Apr 2002 Posts: 27
I have a message driven bean running in WebSphere 5. It fails attempting to put a reply message to a different queue manager. The put is failing because the connection held by the pool manager is invalid as a result of the queue manager it connects to having been re-cycled.
Normally I would expect that the get would be backed out and the message returned to the request queue. On the second attempt the pool manager would have realized the connection was unhappy and created a new one. For some reason the backout is not happening.
I have read as much as I can find and have the configuration set this way. Within MQ I have set the Backout Requeue Name set to a local queue. I have the Backout Threshold set to 2. Within WebSphere AS I have the Maximum Retries on the listener port set to 3. My understanding is that this will allow 2 retries and then move the message to the queue identified by the Backout Requeue Name.
Do I have this configured correctly or am I missing something?
Normally I would expect that the get would be backed out and the message returned to the request queue. On the second attempt the pool manager would have realized the connection was unhappy and created a new one. For some reason the backout is not happening.
Actually this is a misconception. In order for it to happen as described you need a number of additional things including transactionality (requires new)...
and for the pool to purge itself when it recognizes that the connection is gone...
Now if you have setup your onMessage() method not to support transactionality there is no rollback of the input message...
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