qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Wall (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (QPID-6480) Rework defaultVirtualhost attribute and rethink the interaction with virtual host aliases
Date Tue, 07 Apr 2015 10:26:12 GMT

     [ https://issues.apache.org/jira/browse/QPID-6480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Keith Wall updated QPID-6480:
-----------------------------
    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?




  was:
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?




This feature has rather been orphan 



> Rework defaultVirtualhost attribute and rethink the interaction with virtual host aliases
> -----------------------------------------------------------------------------------------
>
>                 Key: QPID-6480
>                 URL: https://issues.apache.org/jira/browse/QPID-6480
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Broker
>            Reporter: Keith Wall
>
> 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?



--
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


Mime
View raw message