activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From manishbel <>
Subject Database lock is not removed when broker is shutdown by calling shutdown mehtod on it.
Date Thu, 23 Aug 2007 16:20:45 GMT


My broker is configured to use the JournaledJdbc which by default allows the
Master/Slave behavior, i have set the start flag to false so that the broker
is not started automatically by the context as i want to start the broker
asynchronously in its own thread so that the other slaves in the cluster
wouldnt stop the application from coming up.

when the application is shutdown i have a shutdown hook which fires off an
event on which i call the stop method on the broker. 

i see even after calling the stop method the lock row in the database
remains and when i try to  start the application back up the broker cant
come up as the lock is already in the database.

I tried it in the standalone environment too but it doesn't remove the  lock
row from the database. 

Has anyone encountered this problem? Please let me know if you have or if
you have any suggestions or if it was fixed in the later versions of the

Thanks in Advance
View this message in context:
Sent from the ActiveMQ - User mailing list archive at

View raw message