[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14070312#comment-14070312 ] 

Rob Godfrey commented on QPID-5076:
-----------------------------------

I think in general if something is durable it should be persisted to the store.  Whether autodelete and durable is a valid combination should be decided at the time of queue creation.

> [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
>
> 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.2#6252)

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