[
https://issues.apache.org/jira/browse/AMQ-3110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980128#action_12980128
]
ashwini kuntamukkala commented on AMQ-3110:
-------------------------------------------
Arne:
Look at my unit test on AMQ-3111. I use JMX to get around this problem by
verifying if a message is being redelivered, {using JMX MBean Server}, if the
message really exists on the queue or not {Phantom message redelivered even
though it is deleted or moved to another queue}. This lead to bad counts but at
least the subsequent messages from the queue got processed.
Let me know if you found any other work around.
Thanks,
> 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.
-
You can reply to this email to add a comment to the issue online.
