activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dejan Bosanac (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-3921) Duplicated durable subscriptions after broker retart with option keepDurableSubsActive=true
Date Wed, 11 Jul 2012 09:32:35 GMT

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

Dejan Bosanac commented on AMQ-3921:
------------------------------------

The root of the problem was that keepDurableSubsActive property wasn't properly propagated
to the durable sub. More info in [AMQ-2665]
                
> Duplicated durable subscriptions after broker retart with option keepDurableSubsActive=true
> -------------------------------------------------------------------------------------------
>
>                 Key: AMQ-3921
>                 URL: https://issues.apache.org/jira/browse/AMQ-3921
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.5.1, 5.6.0
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>             Fix For: 5.7.0
>
>
> In a slightly modified version of JUnit test case org.apache.activemq.usecases.DurableSubscriptionActivationTest
from activemq-core there will be a failure because reactivated subscription with the same
SubscriptionName and ClientID after broker restart was not correctly recognized and as a result,
a duplicated durable subscriptions was added to consumers list.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message