[
https://issues.apache.org/jira/browse/QPID-6381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell resolved QPID-6381.
----------------------------------
Resolution: Fixed
Resolving this, the detach with closed=true is now actioned as expected and
links detached with closed=false and 'configuration' durability no longer have
their backing queue deleted when attached to an exchange.
I did notice another issue when testing this but will raise it separately.
> [Java Broker] [AMQP 1.0] the 'closed' field is ignored when detaching
> ---------------------------------------------------------------------
>
> Key: QPID-6381
> URL: https://issues.apache.org/jira/browse/QPID-6381
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.31
> Reporter: Robbie Gemmell
> Assignee: Rob Godfrey
> Fix For: 0.31
>
>
> The broker does not currently inspect the closed flag of the Detach when
> deciding whether to close detaching consumer links, and instead seems to base
> its action on the terminus durability.
> E.g in SendingLink_1_0.remoteDetached(LinkEndpoint, Detach), it inspects the
> source terminus-durability and closes [almost] everything that is not
> specifying UNSETTLED_STATE durability:
> {noformat}
> //TODO
> // if not durable or close
> if(!TerminusDurability.UNSETTLED_STATE.equals(_durability))
> {
> {noformat}
> This is presumably the reason that QPID-6380 does not result in removal of
> the DurableSubscription backing queue when 'closing' a JMS durable
> TopicSubscriber from the 'existing' AMQP 1.0 JMS client, as it uses
> UNSETTLED_STATE durability on those links.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
