With JBM 1.4.0.CR1 MaxDeliveryAttempts works fine with my MDB. Since 1.4.0.CR2 (CR3, GA, trunk) I have to set DLQMaxResent in MDB, because MaxDeliveryAttempts is ignored. I can also see this message after redelivery: anonymous wrote : | 2007-10-25 15:49:37,118 WARN [org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler] Message redelivered=6 max=5 sending it to the dlq delegator->JBossMessage[2]:PERSISTENT, deliveryId=7 | Queue configuration: | <mbean code="org.jboss.jms.server.destination.QueueService" name="jboss.messaging.destination:service=Queue,name=trStatus" | xmbean-dd="xmdesc/Queue-xmbean.xml"> | <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends> | <depends>jboss.messaging:service=PostOffice</depends> | <attribute name="DLQ">jboss.messaging.destination:service=Queue,name=trStatus</attribute> | <attribute name="RedeliveryDelay">2000</attribute> | <attribute name="MaxDeliveryAttempts">10</attribute> | </mbean> | Is this expected behaviour since 1.4.0.CR2? I have found that this behaviour was introduced by commit: "Fix on JMSXDeliveryCount" date: 2007-08-01, revision: 2943 BTW. As you can see in my config, I am trying to do infinite redelivery by pointing DLQ to the same queue. Is this ok? Maybe there is a better solution? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4098839#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...