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

ASF GitHub Bot commented on ARTEMIS-799:
----------------------------------------

GitHub user tabish121 opened a pull request:

    https://github.com/apache/activemq-artemis/pull/844

    ARTEMIS-799 Fix issues with the AMQP Durable Topic Subscription model

    Fixes several issues found in the handling of durable topic
    subscriptions (test cases added).

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/tabish121/activemq-artemis ARTEMIS-799

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/activemq-artemis/pull/844.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #844
    
----
commit 1f8e2ed5b0bdaf40a76e45b544ce7156c025d7c9
Author: Timothy Bish <tabish...@gmail.com>
Date:   2016-10-12T21:33:08Z

    ARTEMIS-799 Fix issues with the AMQP Durable Topic Subscription model
    
    Fixes several issues found in the handling of durable topic
    subscriptions (test cases added).

----


> AMQP: Problems with durable Topic subscription handling
> -------------------------------------------------------
>
>                 Key: ARTEMIS-799
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-799
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: AMQP
>    Affects Versions: 1.4.0
>            Reporter: Timothy Bish
>
> Handling of durable topic (pub/sub) subscription has a few issues:
> * Cannot reattach a durable subscription from the same connection where one 
> was previously attached and then detached
> * A native AMQP client cannot remove a durable subscription it created simply 
> by closing the link that created the subscription, it must close the link. 
> lookup to subscription and then close the link again, although probably from 
> a different connection given the issue above.
> * When an existing durable topic subscription is looked up it does not return 
> in to the client the selector or noLocal filter that was previously 
> configured on the connection which allows the client to rightly assume that 
> what it got is not the original subscription it created. 
> * Detached links are not freed (closed sessions aren't either) which leads to 
> a slow memory leak given that the broker doesn't ever expect to recover these.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to