The impact of having more than 1 message in the DLQ is that the process that reads from the DLQ will need to keep track of which messages it has processed. This introduces state and since there could be multiple processes reading from the DLQ the state would have to be shared. We are trying to avoid introducing state.
Camel has an idempotent consumer to keep track of which message the processor has seen. I am not sure if ActiveMQ can be configured to check for duplicate messages based on a custom header. I guess it is possible to write a custom BrokerFilter. -- View this message in context: http://activemq.2283324.n4.nabble.com/Behavior-when-a-message-expires-while-it-is-processing-tp4680241p4680314.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
