Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
Description
Currently the Java Broker has a concept of default virtual host, that is, the virtual host to which the a client will connect if they don't specify a virtual host name in the connection url.
Since the introduction if the VHN, the concept of default virtual host is flawed.
If a virtual host node is stopped, the underlying VH does not exist, so its name is not known to the Broker. If I try to edit the Broker's attributes whilst a VNH is stopped, and it happens that the default VH refers to it, the dialogue box contain the default virtual host drop down gets confused as it tries to present a virtual host name that does not exist in the drop down. This forces the user to make a change they do not want.
Brokers should have a default VHN, rather than VH.
Attachments
Issue Links
- is duplicated by
-
QPID-6480 Rework defaultVirtualhost attribute and rethink the interaction with virtual host aliases
- Resolved