Thank you for the input.
I solved the problem of not being able to open multiple Artemis Management
browser tabs by creating unique browser cookies using a class that implements
javax.servlet.ServletContextListener and adding it to the WEB-INF/web.xml file
in Artemis's console.war like so:
<listener>
<listener-class>your.class.with.package.name.here<listener-class>
<listener>
The class's "public void contextInitialized(ServletContextEvent
servletContextEvent)" method is overridden and sets a unique JSESSIONID cookie
name. I used "JSESSIONID.${artemis.broker.name}". For example:
final ServletContext servletContext = servletContextEvent.getServletContext();
final SessionCookieConfig sessionCookieConfig =
servletContext.getSessionCookieConfig();
sessionCookieConfig.setName("JSESSIONID.your.broker.name.here");
Aaron Steigerwald
-----Original Message-----
From: David Martin <dav...@qoritek.com>
Sent: Tuesday, April 26, 2022 6:58 AM
To: users@activemq.apache.org
Subject: [EXTERNAL]:Re: Artemis Cluster Management UI
[CAUTION: This email originated from outside of the organization. Do not click
links or open attachments unless you recognize the sender and know the content
is safe.] ________________________________
Ah yes this is via a lb on different ports. Thanks for the pointer.
On Tue, Apr 26, 2022, 11:30 AM Dondorp, Erwin <erwin.dond...@cgi.com.invalid>
wrote:
> Dave,
>
> > One thing that could help a bit would be to bookmark a set of tabs
> > in
> the browser but unfortunately when logging into a broker any existing
> session for another broker is invalidated.
> > Perhaps there is a broker-side setting in hawtio to allow multiple
> concurrent sessions for different brokers in one browser?
> That happens only when the brokers are on the same machine.
> The reason is that a host-based cookie is replaced with a new value
> for the next session.
> This is due to the fact that cookies are not bound to a port number,
> only to a hostname.
>
> This can be solved by adding hostname-aliasses to your host-file.
> Then each broker seems to have a unique hostname.
> That way, the browser no longer overwrites the cookies and the
> sessions are not lost.
>
> e.
>
> -----Oorspronkelijk bericht-----
> Van: David Martin <dav...@qoritek.com>
> Verzonden: dinsdag 26 april 2022 11:01
> Aan: users@activemq.apache.org
> Onderwerp: Re: Artemis Cluster Management UI
>
>
> EXTERNAL SENDER: Do not click any links or open any attachments unless
> you trust the sender and know the content is safe.
> EXPÉDITEUR EXTERNE: Ne cliquez sur aucun lien et n’ouvrez aucune pièce
> jointe à moins qu’ils ne proviennent d’un expéditeur fiable, ou que
> vous ayez l'assurance que le contenu provient d'une source sûre.
>
> One thing that could help a bit would be to bookmark a set of tabs in
> the browser but unfortunately when logging into a broker any existing
> session for another broker is invalidated. Perhaps there is a
> broker-side setting in hawtio to allow multiple concurrent sessions
> for different brokers in one browser?
>
> Dave
>
>
>
> On Mon, Apr 25, 2022, 2:47 PM Justin Bertram <jbert...@apache.org> wrote:
>
> > The ActiveMQ Artemis web console can only manage one broker at a time.
> > To my knowledge there are no tools to manage multiple brokers
> > simultaneously in real-time. There are, of course, tools to manage
> > and deploy broker configurations behind-the-scenes so to speak (e.g.
> Ansible, Puppet, etc.).
> >
> >
> > Justin
> >
> > On Fri, Apr 22, 2022 at 12:29 PM Steigerwald, Aaron
> > <asteigerw...@brandesassociates.com.invalid> wrote:
> >
> > > Hello,
> > >
> > > What ways exist to manage all Artemis cluster instances from one UI?
> > > I know a different browser tab can connect to each Artemis instance.
> > > My
> > hope
> > > is a more streamlined way exists.
> > >
> > > Thank you,
> > > Aaron Steigerwald
> > >
> >
>
