Hi, this particular of waiting the lock on the database will not be propagated, as it's a regular scenario for master/slave setups
http://activemq.apache.org/shared-file-system-master-slave.html <http://activemq.apache.org/shared-file-system-master-slave.html>All other exceptions will result in startup failure. 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 On Fri, Jul 8, 2011 at 6:44 PM, alexw87 <[email protected]> wrote: > Hi > > I'm starting an embedded Broker using spring, and KahaDBPersistenceAdapter > for persistance. > > This all works fine, but I was hoping to see if there was a way of > detecting > startup errors, say if another instance was started. > > eg : > Database activemq-data\auditBroker\KahaDB\lock is locked... waiting 10 > seconds for the database to be unlocked. > > Is there anyway of bubbling up these exceptions so I can terminate the > application, as currently when using this approach, the executing thread > just sits waiting for the lock to unlock, which it won't > > Any Help or suggestions would be most welcome. > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Detecting-problems-during-BrokerService-startup-tp3654613p3654613.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
