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 -------------------------------------------------------------- Why do you get that impression? 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 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 [https://community.jboss.org/message/715339#715339] Start a new discussion in JBoss Messaging at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&...]