activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dejan Bosanac <>
Subject Re: Issues with stand alone web console in 5.7 using a master/slave architecture
Date Wed, 09 Jan 2013 16:36:35 GMT
Hi Travis,

I think the main change is that now slave broker exposes it's JMX and
shows that it's slave. In older version, the slave MBean server was
not running when broker was slave, so you were connected to the master
instead. I'm not sure there's a workaround for what are you trying to
achieve (other than using different consoles)

Dejan Bosanac
Red Hat, Inc.
FuseSource is now part of Red Hat
Twitter: @dejanb
ActiveMQ in Action:

On Wed, Jan 9, 2013 at 4:30 PM, Travis Klotz <> wrote:
> We are running the web console as  stand alone application in a
> glassfish container using system properties to configure connection
> info to point to our two server master/slave setup.   We do this so
> that we easily have a single URL to look at regardless of which server
> is the master and which is the slave.
> This has worked great for us in 5.5 and 5.6 but when upgrading to 5.7
> we have run into a problem.   When server1 is the master, everything
> works great,  but when server1 is the slave,  we always get redirected
> to slave.jsp and are informed that the server is currently in slave
> mode.   This in in spite of the fact that we have configured the web
> app to point to both servers using both JMX and JMS.
> For Example:
> -Dwebconsole.jms.url=failover:(tcp://server1:61616,tcp://server2:61616)
> -Dwebconsole.jmx.url=service:jmx:rmi:///jndi/rmi://server1:1099/jmxrmi,service:jmx:rmi:///jndi/rmi://server2:1099/jmxrmi
> Is there a new configuration option we need to set?  Or perhaps
> something didn't get updated properly in the 5.7 web console?
> Thanks,
> Travis

View raw message