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 2014/07/19 13:01:39 UTC
[jira] [Comment Edited] (QPID-4299) [Java Broker Web Console] The 2
virtual host aliases with the same names are displayed for virtual host
when both http and https are enabled
[ https://issues.apache.org/jira/browse/QPID-4299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14067481#comment-14067481 ]
Keith Wall edited comment on QPID-4299 at 7/19/14 11:00 AM:
------------------------------------------------------------
At 0.29, Virtual host aliases are no longer created for non AMQP ports, so this defect can no longer manifest. It is possible this issue was fixed prior to 0.29.
However, if a user creates many AMQP ports, this will cause many VHA model objects to be created with the same name (as the alias is named after the VH name). I'll raise a separate JIRA for this issue.
was (Author: k-wall):
At 0.29, Virtual host aliases are no longer created for non AMQP ports, so this defect can no longer manifest. However, if a user creates many AMQP ports, this will cause many VHA model objects to be created with the same name. I'll raise a separate JIRA for this issue.
> [Java Broker Web Console] The 2 virtual host aliases with the same names are displayed for virtual host when both http and https are enabled
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: QPID-4299
> URL: https://issues.apache.org/jira/browse/QPID-4299
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.18, 0.19
> Reporter: Alex Rudyy
> Priority: Minor
> Fix For: 0.29
>
>
> On starting Java broker with enables http and https web interfaces the 2 aliases with the same name "test" are displayed for virtual host "test" in Web management Console.
> The further analysis showed that aliases are created for HTTP and HTTPS ports:
> To get more details I added "port" and "authenticationMethods" attributes into VirtualHostAliasAdapter and started the broker. That gave me the details of aliases:
> "virtualhostaliass" : [ {
> "id" : "53bfdd22-d1d8-397b-9d3e-5763ad4d5417",
> "name" : "test",
> "port" : "0.0.0.0:8080",
> "authenticationMethods" : [ ]
> }, {
> "id" : "47440d0b-7c80-3949-b961-eeae965e9fb5",
> "name" : "test",
> "port" : "0.0.0.0:8443",
> "authenticationMethods" : [ ]
> } ]
> At the moment virtual host aliases are created for the each broker port( BrokerAdapter#getPorts()). On VirtualHostAdapter creation, broker ports (returned by BrokerAdapter#getPorts()) are iterated and for each port the alias is created. The ports returned by BrokerAdapter#getPorts() contain both HTTP and HTTPS ports which are added into broker ports from the ApplicationRegistry on BrokerAdapter creation. AMQP ports are retrieved from the acceptors which are created after the broker initialization (after broker and virtual host adapters are created)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org