activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "costas.sterpis" <constantinos.ster...@gmail.com>
Subject Web Console Availability and master-slave brokers with shared file system
Date Wed, 14 Dec 2011 14:27:28 GMT
When having a scenario of two activemq brokers following the shared file
system master-slave pattern, 
is it possible to have their web consoles always available and pointing to
the active broker each time, provided that both brokers are up and running?

According to the documentation ( http://activemq.apache.org/web-console.html
http://activemq.apache.org/web-console.html ), there is a way to provide the
web console with failover configuration for master-slave brokers using these
parameters:
/-Dwebconsole.jms.url=failover:(tcp://serverA:61616,tcp://serverB:61616)
-Dwebconsole.jmx.url=service:jmx:rmi:///jndi/rmi://serverA:1099/jmxrmi,
service:jmx:rmi:///jndi/rmi://serverB:1099/jmxrmi
/

Unfortunately, appending these options to the startup script of the activemq
distro prevents the broker from starting, as the '(' character cannot be
parsed during script execution.

Any help would be much appreciated.



--
View this message in context: http://activemq.2283324.n4.nabble.com/Web-Console-Availability-and-master-slave-brokers-with-shared-file-system-tp4195199p4195199.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Mime
View raw message