"weston.price(a)jboss.com" wrote : | | The DLQ handler is layered with a JBoss specific handler being called first to handle redelivery. First we check for the existence of the JMS_JBOSS_REDELIVERY_LIMIT and JMS_JBOSS_REDELIVERY_COUNT. | You mean JBoss MQ specific? JBoss Messaging doesn't have these properties. "weston.price(a)jboss.com" wrote : | If we can find the count we compare it againts the ActivationSpec property DLQMaxResent. If it's over the limit, the JBoss specific DLQ handles the message. | | If we don't execute the above, the GenericHandler kicks in. We try and check the JMSXDeliveryCount first. If it exists, all is well and we use that as a marker for re-delivery attempts. | | Now, heres the trick :-). | | If that property does not exist, we increment a counter based on the cached ID for that message. So, basically in order: | | JBoss specific | Generic JMSXDeliveryCount | Cached id/count mapping | So you maintain a map of id to count? How long do you keep items in the map for? It could grow pretty big. Also wouldn't survive restart I assume. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986878#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...