[QPID-6480] Rework defaultVirtualhost attribute and rethink the interaction with virtual host aliases

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Component/s: Broker-J
• Assignee: Unassigned
• Reporter: Keith Wall
• Created: 07/Apr/15 08:26
• Updated: 13/Nov/15 16:46
• Resolved: 31/May/15 22:05

Description

Currently Java Broker has an attribute defaultVirtualhost. This is the name o fthe virtualhost that a messaging client will be connected to if they omit the virtual host name during connection.open.

The feature has not worked too well since the introduction of virtual host nodes. In the HA use-case, if a user edits the Broker's attributes whilst a node is non-master, they can be forced to elect a new default virtual host simply because at that moment. the Broker does not recognise the name,

Should the defaultVirtualhost become a defaultVirtualhostNode? How should this feature interact with the virtual host aliases?

Issue Links

• duplicates: QPID-6443 Broker should have a default VHN rather than default VH