You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2010/06/01 19:28:51 UTC

[jira] Created: (AMQ-2755) Durable Subs repeated drain and reconnect, skipping messages with kahaDB

Durable Subs repeated drain and reconnect, skipping messages with kahaDB
------------------------------------------------------------------------

                 Key: AMQ-2755
                 URL: https://issues.apache.org/activemq/browse/AMQ-2755
             Project: ActiveMQ
          Issue Type: Bug
          Components: Broker
    Affects Versions: 5.3.2
            Reporter: Gary Tully
            Assignee: Gary Tully
             Fix For: 5.4.0


With kahaDB as the default store some of the durable tests fail. The issue is the next message sequence gets out of sync when a durable sub is repeatedly drained such that an new message can be incorrectly seen as an ack. A consumer can miss a message as a result.

Tests that fail: org.apache.activemq.usecases.DurableConsumerCloseAndReconnectTest.testCreateDurableConsumerCloseThenReconnect
 org.apache.activemq.network.SimpleNetworkTest.testDurableStoreAndForwardReconnect


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (AMQ-2755) Durable Subs repeated drain and reconnect, skipping messages with kahaDB

Posted by "Gary Tully (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQ-2755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Tully resolved AMQ-2755.
-----------------------------

    Resolution: Fixed

resolved in r950171

> Durable Subs repeated drain and reconnect, skipping messages with kahaDB
> ------------------------------------------------------------------------
>
>                 Key: AMQ-2755
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2755
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.3.2
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>             Fix For: 5.4.0
>
>
> With kahaDB as the default store some of the durable tests fail. The issue is the next message sequence gets out of sync when a durable sub is repeatedly drained such that an new message can be incorrectly seen as an ack. A consumer can miss a message as a result.
> Tests that fail: org.apache.activemq.usecases.DurableConsumerCloseAndReconnectTest.testCreateDurableConsumerCloseThenReconnect
>  org.apache.activemq.network.SimpleNetworkTest.testDurableStoreAndForwardReconnect

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.