[ https://issues.apache.org/jira/browse/AMQ-3110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish closed AMQ-3110. ----------------------------- Resolution: Cannot Reproduce The test case provided sets redelivery on the client as unlimited so the fact that the messages is being redelivered is expected as re-deliveries are done locally so a JMX move would not affect the client. Modifying the test case such that the message is prefetched but the transaction is not committed and then a new consumer is attached to the same queue result in no redelivery of the moved message. > Same message redelivered again even though moved to a different queue using > web console > --------------------------------------------------------------------------------------- > > Key: AMQ-3110 > URL: https://issues.apache.org/jira/browse/AMQ-3110 > Project: ActiveMQ > Issue Type: Bug > Components: Broker > Affects Versions: 5.3.0 > Environment: Windows XP > Java 1.6 > Reporter: ashwini kuntamukkala > Priority: Critical > Attachments: > FailingMessageRedeliveredDespiteBeingMovedToExceptionQueue.java > > > I have a queue which has 1 asynchronous consumer. Underlying connection has a > redelivery policy where max retries is set to -1 (Indefinite). > When a bad message is stopping the rest of the messages in the queue, I use > webconsole/jconsole to move the message to an exception queue. However, the > same bad message is being resent to the consumer. > The problem goes away only when I restart the broker. This is not an > acceptable solution. > I have attached a junit test so you can understand this scenario better. > Thanks, > Ashwini Kuntamukkala -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira