4 Replies Latest reply on Aug 10, 2009 7:15 AM by bershath27

Max Delivery Attempts ignored on Jboss 5.1 queue?

dejanmr Aug 5, 2009 11:10 AM

I have very simple queue.

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>

Work 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?

1. Re: Max Delivery Attempts ignored on Jboss 5.1 queue?

gaohoward Aug 5, 2009 11:41 AM (in response to dejanmr)

It should work with JBM.

You can do a simple test with the 'queue' example in JBM distro and see if it works.

Ask MDB/JCA forum for any MDB configurations that may supersede this param.
Actions
2. Re: Max Delivery Attempts ignored on Jboss 5.1 queue?

ataylor Aug 6, 2009 4:12 AM (in response to dejanmr)

MDB's handle there own delivery. I think there is an activation property you can set. MDb's are notp art of messaging so the guys on the JCA forums or AS forums would be able to help. Or you could take a look at the AS docs.
Actions
3. Re: Max Delivery Attempts ignored on Jboss 5.1 queue?

dejanmr Aug 7, 2009 6:35 AM (in response to dejanmr)

Thanks for the hint.

Issue is resolved at:http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4248648#4248648
Actions
4. Re: Max Delivery Attempts ignored on Jboss 5.1 queue?

bershath27 Aug 10, 2009 7:15 AM (in response to dejanmr)

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

This is the expected behavior. The MaxDeliveryAttempts defined at the destination gets overridden by the ActivationConfigParameters defined at your MDB. If you haven't specified this on your MDB, it uses the default value, which is 5.

Even though you could override MaxDeliveryAttempts in your MDB configuration, it can't exceed the MaxDeliveryAttempts defined at the given destination. ;-)
Actions

Go to original post