Posted: Tue Sep 03, 2013 3:09 am Post subject: how to set redelivery interval for failed messages
Newbie
Joined: 03 Sep 2013 Posts: 2
Hi,
we are using weblogic MDB andIBM MQ in our project.We have encountered cases when MDB is not able to process the message due to DB issues and we roll back the message by throwing the runtime exception.
This happens for predefined no of times by trakcing redelivery count propery on message header.But i could not find a way to set the redelivery interval for those failed messages.e.g. if i havea DB issue ,i want MQto resend the message only after 30 mins after its failure.so if my redeliverycount is set to 30.witrh30 mins of redelivery interval i will getapprox 900 mins to recover from DB issue.
Can someone help me understand how i can get around this issue or make sure message is not lost.I cant set theredelivery count very high as this will impact the performance.
Posted: Tue Sep 03, 2013 4:53 am Post subject: Re: how to set redelivery interval for failed messages
Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
padmesh agnihotri wrote:
i want MQto resend the message only after 30 mins after its failure.so if my redeliverycount is set to 30.witrh30 mins of redelivery interval i will getapprox 900 mins to recover from DB issue.
WMQ doesn't do that. You'll need some kind of timing mechanism either in weblogic or whatever mechanism is retrying from the backout queue. _________________ Honesty is the best policy.
Insanity is the best defence.
when you say timing mechanism on weblogic.what exactly you referring to?.while i understand there are work arounds like dead letter queue or some other stuff to process the message outside the MDB conext.
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
padmesh agnihotri wrote:
when you say timing mechanism on weblogic.what exactly you referring to?
Back in my day weblogic had internal mechanisms for dealing with backed out messages. Times may have changed.
padmesh agnihotri wrote:
while i understand there are work arounds like dead letter queue or some other stuff to process the message outside the MDB conext.
Indeed. My tip with that would be to use a specific "dead letter" queue rather than the actual one associated with the queue manager. _________________ Honesty is the best policy.
Insanity is the best defence.
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