wood burning stoves 2.0
The moose likes EJB and other Java EE Technologies and the fly likes Delay on MDB message rollback Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of REST with Spring (video course) this week in the Spring forum!
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "Delay on MDB message rollback" Watch "Delay on MDB message rollback" New topic

Delay on MDB message rollback

Terence Lai

Joined: Dec 09, 2007
Posts: 8

I am trying to figure out whether WebSphere MQ has configuration options to set the delay of the message being *put back to* or *pick up from* the original destination when the setRollbackOnly() method is called in MDB. I am using WebSphere Application Server v6.1 with WebSphere MQ.

I have checked the following article, and it still doesn't give me the answer:

The article said "the messaging engine custom property sib.processor.blockedRetryTimeout tells the application server how long to wait before redelivering a poison message to an MDB, if and only if the Exception destination property is set to "None.""

This is not what I need. I would like to specify the Exception destination. When the message reaches the Max. Failed Deliveries threshold, the message will be delivered to a different queue. This will give the administrator the capability to re-queue the message at a later time. On the other hand, if the Max. Failed Deliveries threshold hasn't been reached, I want the message being put back to the original queue with some delay before it is being process again.

The reason that I want to have the delay is that my MDB is used to process the file FTP delivery request. If the FTP connection fails, I want to have a number of retries with some delays. It doesn't make sense to retry immediately.

Any helps would be appreciated.


Does any one have an answer on
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
subject: Delay on MDB message rollback
It's not a secret anymore!