You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Keith Wall (JIRA)" <ji...@apache.org> on 2016/06/08 10:29:21 UTC
[jira] [Updated] (QPID-7138) [Java Broker] Broker should detect
duplicate IDs in configured objects
[ https://issues.apache.org/jira/browse/QPID-7138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Wall updated QPID-7138:
-----------------------------
Fix Version/s: (was: qpid-java-6.1)
qpid-java-7.0.0
> [Java Broker] Broker should detect duplicate IDs in configured objects
> ----------------------------------------------------------------------
>
> Key: QPID-7138
> URL: https://issues.apache.org/jira/browse/QPID-7138
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Affects Versions: 0.28, 0.30, 0.32, qpid-java-6.0, qpid-java-6.0.1
> Reporter: Alex Rudyy
> Fix For: qpid-java-7.0.0
>
>
> Currently UUID uniqueness is enforced only amongst immediate siblings. This means that, say, a virtual host with queue with UUID A would reject a second queue with the same UUID A. Currently if a second virtual host had a queue with same UUID A, this would be allowed. This presents a problem for clients (including the Web Management Console) that expect UUID to be universally unique.
> Change ACO so that object UUID are universally so. The validatation would need to be applied as new objects are created, as the Broker starts up and as Virtualhosts are recovered. This latter may or may not be at start-up time.
--
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