[
https://issues.apache.org/jira/browse/QPID-5582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell reassigned QPID-5582:
------------------------------------
Assignee: Rob Godfrey (was: Robbie Gemmell)
As discussed, Exchange deletion looks like it will orphan bindings within the
store despite individually performing/logging their deletion. This is due to
the way calling exchange.delete() goes through the vhost and back to
exchange.close(), at which point it calls delete on the bindings individually
but only immediately after unregistering itself as a listener and thus
preventing itself from actually removing them when the binding calls its change
listener.
> [Java Broker] Enforce 0-10 restriction on uniqueness of binding keys
> ---------------------------------------------------------------------
>
> Key: QPID-5582
> URL: https://issues.apache.org/jira/browse/QPID-5582
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Reporter: Rob Godfrey
> Assignee: Rob Godfrey
> Fix For: 0.27
>
>
> Currently the Java broker does not uniformly enforce the 0-10 restriction
> that the tuple (exchange, queue, binding-key) must be unique (this is
> because there was no such restriction in 0-8).
> Enforce this restriction and upgrade existing durable bindings where possible
> (conflicts should only occur where there are multiple bindings that differ
> only in their arguments. For the headers exchange where there are multiple
> bindings, we can generate unique names. For other exchanges we can combine
> multiple bindings (as the arguments would be JMS selectors which can be
> textually ORd).
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
