[
https://issues.apache.org/jira/browse/AMQ-5142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish closed AMQ-5142.
-----------------------------
Resolution: Invalid
This is a user list question not a bug report.
> Behavior when message expires while it's being processed
> --------------------------------------------------------
>
> Key: AMQ-5142
> URL: https://issues.apache.org/jira/browse/AMQ-5142
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.7.0
> Environment: OS: Linux 3.5.0 (Mint 14)
> Java: 1.6
> Camel: 2.8.2
> Reporter: Mike Chao
>
> I have 2 jms queues, queue.start and queue.end. Using camel I setup a route
> from queue.start -> sleepProcessor -> queue.end. I also have individual dead
> letter queues setup for queue.start and queue.end. The sleepProcessor takes
> the message and sleeps for 5 seconds.
> I send 1 message with a JMSExpirationTime of 1 second from
> System.currentTimeMillis(). The behavior I see is that 1 message ends up in
> DLQ.queue.start and another message ends up in DLQ.queue.end.
> Transactions are enabled.
> The test program can be found here
> http://s000.tinyupload.com/?file_id=04225732819763428273
> And can be run with
> mvn camel:run
> Is there a way to configure activeMQ so that only 1 message ends up in the
> dead letter queue?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
