If the JMS_JBOSS_REDELIVERY_LIMIT in the JMS message header is set to a value higher then the MaxTimesRedelivered setting of the DLQConfig in the invoker-proxy-binding used by the MDB, the MDB will retry 1+ the MaxTimesRelivered max value, and then drop the message instead of forwarding it to the DLQ.
For example, if the MaxTimesRedelivered is set to 3 and the JMS_JBOSS_REDELIVERY_LIMIT is set to 5, the MDB retries 4 times and the message is dropped and not forwarded to the DLQ. I would understand if the behaviour would be retrying 3 times max and then forwarded to the DLQ , even with the JMS_JBOSS_REDELIVERY_LIMIT set higher then 3. However, since it is retry 4 times and dropping the message, this seems to be a bug in how the JMS_JBOSS_REDELIVERY is being used the the JMS subsystem. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3844168#3844168 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3844168 ------------------------------------------------------- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
