[
https://issues.apache.org/jira/browse/ARTEMIS-3078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17268855#comment-17268855
]
Erwin Dondorp commented on ARTEMIS-3078:
----------------------------------------
[~jbertram]
I was already using FireFox, so that is easy. The effect is still present in
private browsing.
I noticed the 2 sessions have a JSESSIONID cookie with the same value. It seems
that cookies are not separated by port number. Never knew that.
The article
[https://stackoverflow.com/questions/1612177/are-http-cookies-port-specific]
confirms that, so the current behaviour seems unavoidable.
Addressing the servers as "localhost" and "127.0.0.1" solves the issue. When
there are more than 2 copies, I'll just have to add more silly aliases for
localhost...
> 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)
