There should not ever be any resends (if someone did not sneek in any special stuff I have not seen). The logic with the DLQ handler is as follows:
- If a message is resent a configurable number of times it will be placed in a "dead letter queue". This is done since JBossMQ do not have a mechanism to not flood a subsciber when it does not ack messages, which will eventually grind JBoss to a halt.
- The dead letter queue is a normal JMS Queue destination.
- The DLQ is configurable.
- It is up to administrative rutines (either developed in JBoss admin or as a part of the application) to administer the messages in the DLQ.
- Dead message will basically live for ever in the queue until they are fetched.
- DLQ is described in a change note on sourceforge and is documented in the class org.jboss.ejb.plugins.jms.DLQHandler.java.
I had no idea these stuff would find its way into the 2.4 line. I will try to document the new stuff when I get the time.
> There should not ever be any resends (if someone did
> not sneek in any special stuff I have not seen).
Assuming you speak of the resends done when JBoss restarts, it's not meant to do that? In that case, I guess I shouldn't rely on that behavior to stay.
> - DLQ is described in a change note on sourceforge
> and is documented in the class
I'll have a look at that. Thanks!