activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMQ-4665) Failover with client ack mode consumer can loose a message auto acked as a duplicate
Date Wed, 07 Aug 2013 13:42:48 GMT

     [ https://issues.apache.org/jira/browse/AMQ-4665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Gary Tully resolved AMQ-4665.
-----------------------------

    Resolution: Fixed

fix in http://svn.apache.org/r1511307

auto ack on duplicate now replaced with poison ack with poison cause property set. Duplicates
need to be flagged as problems in the normal case.
Client ack mode now allows replay b/c consumed and undelivered are rolledback in a failover
interrupt.
                
> Failover with client ack mode consumer can loose a message auto acked as a duplicate
> ------------------------------------------------------------------------------------
>
>                 Key: AMQ-4665
>                 URL: https://issues.apache.org/jira/browse/AMQ-4665
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: JMS client
>    Affects Versions: 5.8.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>              Labels: clientAck, duplicate, failover
>             Fix For: 5.9.0
>
>
> with a client ack consumer and failover after receipt but before message.ack can result
in a missed message when the message is redispatched and auto acked as a duplicate.
> Failover interrupt should clear dispatched and unconsumed messages so that they can get
redelivered.
> auto-acking a duplicate seems over eager. think best to poison pill and now that we can
include a cause property it will be possible to differentiate.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message