Re: Checking that slave is up

2012-01-18 Thread Dejan Bosanac
I don't think so, there can also be times when JMX is up but that bean is still not registered. You should be catching this in your app. Regards -- Dejan Bosanac - http://twitter.com/dejanb - The experts in open source integration and messaging - http://fusesource.com ActiveMQ in

Re: Checking that slave is up

2012-01-05 Thread Stevo Slavić
When broker is starting up with existing JVM (non-ActiveMQ created) MBeanServer, and isSlave gets called by a scheduled job, I get InstanceNotFoundException on the client side. Nothing declares this checked exception will get thrown so compiler won't let me catch it. Once ActiveMQ is fully up, same

Re: Checking that slave is up

2012-01-05 Thread Stevo Slavić
Great, thank you very much Dejan! This property is not listed on the ActiveMQ JMX Reference page: http://activemq.apache.org/jmx.html#JMX-ActiveMQMBeansReference Found more info in the source and contributed fix for javadoc typo ( see https://issues.apache.org/jira/browse/AMQ-3652 ). FOSS rulz!

Re: Checking that slave is up

2012-01-05 Thread Dejan Bosanac
It does, and you have "Slave" JMX attribute on broker object. Regards -- Dejan Bosanac - http://twitter.com/dejanb - The experts in open source integration and messaging - http://fusesource.com ActiveMQ in Action - http://www.manning.com/snyder/ Blog - http://www.nighttale.net O