Hi, I am trying to understand the behavior when a message expires while it is being processed. I have the following flow setup in my test program.
queue.start -> sleepProcessor -> queue.end The sleepProcessor takes the message from queue.start and sleeps for 5 seconds. I send a message to queue.start with a JMSExpiration of 1 second from System.currentTimeMillis(). I have setup dead letter queues for each queue named DLQ.queue.start and DLQ.queue.end. The behavior I see is that 1 message ends up in DLQ.queue.start and another message ends up in DLQ.queue.end. How does 1 message become 2? The test program can be found here with source testJMSExpiration.zip <http://activemq.2283324.n4.nabble.com/file/n4680241/testJMSExpiration.zip> I have included a maven pom.xml and the test program can be run with the following command mvn camel:run OS: Linux 3.5.0 (Mint 14) JVM: 1.6 ActiveMQ: 5.7.0 Camel: 2.8.2 Any insight would be greatly appreciated. Thank you -- View this message in context: http://activemq.2283324.n4.nabble.com/Behavior-when-a-message-expires-while-it-is-processing-tp4680241.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
