[ 
https://issues.apache.org/jira/browse/AMQ-3110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980140#action_12980140
 ] 

Gary Tully commented on AMQ-3110:
---------------------------------

note that redelivery in activemq is implemented on the client side, by the 
message consumer. It is only when the redelivery count is exceeded that a 
posion ack is sent to the broker.
If during redelivery, the consumer dies or the broker is restarted, the message 
will get redispatched by the broker as it has not been acknowledged.
If the message has been removed, then it should not get redelivered in the 
above cases.
I think there is a bug in the queue.removeSubscription where it deals with 
inflight messages. There it needs to check to ensure the message is not 
acknowledged such that it won't be dispatched if it was inflight when the 
subscription goes away. A remove, done as part of a move, will mark the message 
as acknowledged.

> 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.

Reply via email to