Gary - Thanks for the pointers. For my in-house work, I am testing
with the comma-separated list of jmx url's and just establishing
connections to them in-order and returning the MBeanServerConnection
for the first one that works. I also have a daemon thread to monitor
this connection failure and t
hmm. I see we already have an issue for the RemoteJMXBrokerFacade at
https://issues.apache.org/jira/browse/AMQ-2785
vote it up I guess or if you can, submit a patch. All contributions
most welcome.
On 5 September 2012 12:00, Gary Tully wrote:
> There is no easy solution for this at the moment.
>
There is no easy solution for this at the moment.
Since https://issues.apache.org/jira/browse/AMQ-2306 both the master
and slave expose them selves over JMX so both urls will be valid.
The difference is that only one will report isSlave==false
There is a jmx facade used by the web console that co
Finally found the answer:
The remote breakpoint i put on my embedded ActiveMQ consumer was a default
breakpoint with suspend-policty=all.
And as the consumer and the server runs on the same JVM, i was also
suspending all the ActiveMQ server threads!
The solution is to use a breakpoint suspend-po
