The AS JCA layer also has it's own redelivery logic (this is the one that's controlled by DLQMaxResent) - this is so that JCA layer can be used consistently with a range of different JMS providers who may not have their own redelivery or DLQ functionality.
JBM also has it's own DLQ and redelivery functionality. By default I believe the JCA redelivery will take precedence over JBM delivery. I beieve the JCA default is 5 - this would make sense with what you're seeing. I would say the current behaviour is now correct. Previously before Clebert's patch the JMSXDeliveryCount property wasn't be stored properly in the message hence the JCA layer didn't know the messages delivery count and the JCA delivery did not kick in. If you don't want the JCA delivery you can turn it off in the config, and just use the JBM one. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4102347#4102347 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4102347 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
