Max Delivery Attempts ignored on Jboss 5.1 queue?

[dejanmr]

I have posted this message already on JBoss Messaging forum, but they suggested to change forum. Guess EJB3 people might help. They suggested this should work fine and that this is MDB issue.

I have very simple queue. Both producer an consumers are EJB3 (Stateless session and MDB)

I have set attribute:

<attribute name="MaxDeliveryAttempts">13</attribute>

in *-service.xml file. Value is visible form JBoss AS Administration console, configuration view of a queue (Max Delivery Attempts).

But, when message delivering files (Ejb3 MDB), after only 5 (not 13 as expected), I got message:

WARN [AbstractDLQHandler] Message redelivered=6 max=5 sending it to the dlq delegator->JBossMessage[20471539334316035]:PERSISTENT, deliveryId=25

Afterward, message is moved to DLQ as expected.

It is not even 10, which is expected default value.
Some other attributes, like

<attribute name="RedeliveryDelay">17000</attribute>

Works as expected (delay between two attempts to deliver message is 17 seconds).

Is this me doing something wrong, or JBoss is ignoring this parameter?

How to set it up?

[jaikiran]

On your EJB3 MDB you have to configure the dLQMaxResent activation config property (which by default is 5) http://www.jboss.org/file-access/default/members/jbossejb3/freezone/docs/tutorial/1.0.7/html/Message_Driven_Beans.html

[dejanmr]

"jaikiran" wrote:
On your EJB3 MDB you have to configure the dLQMaxResent activation config property (which by default is 5) http://www.jboss.org/file-access/default/members/jbossejb3/freezone/docs/tutorial/1.0.7/html/Message_Driven_Beans.html

Thank you, this have done the trick.

Moreover, tests proved that Max Delivery Attempts is not being ignored.

Both values are considered, and lower maximum is taken into account. So, basically maximum number of attempts is min(dLQMaxResent, MaxDeliveryAttempts).