[
https://issues.apache.org/jira/browse/ARTEMIS-3078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17268859#comment-17268859
]
Justin Bertram commented on ARTEMIS-3078:
-----------------------------------------
Thanks for the follow up. Given this is limited to the use-case where multiple
brokers are running on a single host and being referenced with the same
IP/hostname as well as the fact that [the current cookie
specification|http://tools.ietf.org/html/rfc6265] doesn't allow isolating
cookies by port I'm going to close this Jira as "Won't fix."
> Log in on second web console closes first session, even for different brokers
> -----------------------------------------------------------------------------
>
> Key: ARTEMIS-3078
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3078
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Web Console
> Affects Versions: 2.16.0
> Reporter: Erwin Dondorp
> Priority: Minor
>
> When there are 2 brokers running, logging in into the web console of the
> second broker will cause an immediate logout in the session for the first
> broker.
> * start 2 containers, echo one with an independent Artemis installation
> use port mapping in docker to give each a unique port number
> * open webconsole session for first broker and log in
> * open webconsole session for second broker and log in
> * see that the first session automatically logs out and returns to the login
> screen
> the affect is symmetric and can be repeated as many times as wanted
> When working on a network-of-brokers, this is fairly annoying...
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
