[
https://issues.apache.org/jira/browse/QPID-7138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7138:
-----------------------------
Description:
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 validate 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.
was:Currently duplicate IDs are only checked on configuration store levels,
i.e. broker configuration store, virtual host configuration stores. However, if
duplicate IDs are used in different virtual host configuration stores that will
be unnoticed by the broker. Configured object names are used to refer
configured objects from each other at the moment but IDs can be used for object
referencing as well, for example, in result of manual editing of configuration
files. We need to enforce ID integrity check and detect any duplicate IDs on
broker on startup .
> [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-6.1
>
>
> 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 validate 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: [email protected]
For additional commands, e-mail: [email protected]
