[
https://issues.apache.org/jira/browse/ARTEMIS-799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish updated ARTEMIS-799:
---------------------------------
Description:
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.
> 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)
