[jira] [Resolved] (QPID-5076) [Java Broker] Durable auto-delete queues leave behind orphaned bindings

["Rob Godfrey (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/QPID-5076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Godfrey resolved QPID-5076.
-------------------------------
       Resolution: Fixed
    Fix Version/s: 6.0 [Java]

Changes to the way objects are stored in config have removed this inconsistency

> [Java Broker] Durable auto-delete queues leave behind orphaned bindings
> -----------------------------------------------------------------------
>
>                 Key: QPID-5076
>                 URL: https://issues.apache.org/jira/browse/QPID-5076
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>            Reporter: Rob Godfrey
>             Fix For: 6.0 [Java]
>
>
> On line 1240 of ServerSessionDelegate and line 112 of QueueDeclareHandler the following test is applied before deciding whether to store a queue definition to the durable config store:
> {code}
> if (queue.isDurable() && !queue.isAutoDelete())
> {code}
> However a binding is entered into the store based only on the durability of the queue and exchange.  Thus a durable autodelete queue bound to a durable exchange will cause a binding record to be written to the store where there is no corresponding queue record.
> It is a little unclear to me what the correct semantics of durable auto-delete queues actually should be.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org