[jboss-user] [JBoss Messaging] - Re: no success increasing number of redelivery attempts

Justin Bertram do-not-reply at jboss.com
Wed Feb 8 16:44:30 EST 2012

Justin Bertram [https://community.jboss.org/people/jbertram] created the discussion

"Re: no success increasing number of redelivery attempts"

To view the discussion, visit: https://community.jboss.org/message/715339#715339

> ...redelivery attempts aren't limited to 5. I get the impression that redelivery attempts now go on forever.
Why do you get that impression?
> What I would really want is that the config in messaging-service.xml , attribute "DefaultMaxDeliveryAttempts" , is respected (or some more fine-grained config, per queue or per MDB).
Now that your MDB is using useDLQ=false then JBoss Messaging will enforce the "DefaultMaxDeliveryAttempts" which is set in messaging-service.xml.  This setting can be overridden on a per-destination basis using the "MaxDeliveryAttempts" attribute.  Redelivery cannot be set on a per-MDB basis.
>  I saw some reports which maybe indicate this is a known problem in AS 5. Can anyone confirm this?
I haven't heard that.  To my knowledge the redelivery settings should be enforced without issue.

To be clear, there has been confusion around the useDLQ and DefaultMaxDeliveryAttempts settings.  This is because JBoss MQ, the JMS implementation which preceded JBoss Messaging, did not have its own redelivery/DLQ logic.  Therefore, redelivery/DLQ logic was placed in the JBoss EAP generic JMS JCA Resource Adapter.  This logic is active by default and because it uses a lower threshold (i.e. 5) than JBoss Messaging (i.e. 10) that supersedes it.  To rectify this, one must set the activation configuration property named "useDLQ" to "false" (defaults to "true") on the MDB.  This will allow the JBoss Messaging configuration (i.e. DefaultMaxDeliveryAttempts) to take effect.  We currently recommend that every MDB set "useDLQ" to "false" so that the JBoss Messaging redelivery logic is used in lieu of the RA's logic.

Reply to this message by going to Community

Start a new discussion in JBoss Messaging at Community

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-user/attachments/20120208/0dff7e7e/attachment-0001.html 

More information about the jboss-user mailing list