[jira] [Commented] (AMQ-4000) Durable subscription not getting unregistered on networked broker

["Torsten Mielke (JIRA)" <ji...@apache.org>]

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

Torsten Mielke commented on AMQ-4000:
-------------------------------------

org.apache.activemq.advisory.AdvisoryBroker does not override the method 
public void removeSubscription(ConnectionContext context, RemoveSubscriptionInfo info);

of class org.apache.activemq.broker.BrokerFilter.

Its the AdvisoryBroker that is responsible for creating and firing the advisory message to inform other brokers in the network that a durable subscription got removed. 
So AdvisoryBroker needs to override method removeSubscription() accordingly. 

                
> Durable subscription not getting unregistered on networked broker
> -----------------------------------------------------------------
>
>                 Key: AMQ-4000
>                 URL: https://issues.apache.org/jira/browse/AMQ-4000
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.6.0
>         Environment: network of brokers, durable topic subscriptions.
>            Reporter: Torsten Mielke
>              Labels: durable_subscription, networks
>         Attachments: JUnitTest.patch
>
>
> In a network of two brokers, a durable subscription is correctly propagated across to the remote broker. However when the consumer unsubscribes from the durable subscription again, it is only removed on the local broker but not on the remote broker. The remote broker keeps its durable subscription alive.
> As a consequence messages sent to the topic destination on the remote broker for which the durable subscriptions existed, are passed on to the local broker, although there is no active subscription on the local broker. The local broker will discard these msgs but unnecessary traffic has already occurred on the network bridge.

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