It's my understanding that restarts are handled by the Tanuki service wrapper, when ActiveMQ is installed as a service, using the instructions at http://activemq.apache.org/java-service-wrapper.html. Is that how you're using ActiveMQ? Or are you running the broker directly from the executable in the bin directory, which wouldn't use the wrapper (and so wouldn't restart the process)?
Tim On Thu, Feb 28, 2019, 1:57 PM Martin Lichtin <lich...@yahoo.com.invalid> wrote: > Hi > > Can you help me understand this situation? > I've ActiveMQ configured with a lease lock on a DB. Spontaneously it > decided it can no longer keep the lock, and starts shutting down: > > 2019-02-27T16:47:45,491 | INFO | Starting Thread | BrokerService > | he.activemq.broker.BrokerService 773 | 73 - activemq-osgi - 5.15.6 | > Apache ActiveMQ 5.15.6 (broker, amq2) started > > 2019-02-27T16:51:05,907 | ERROR | KeepAlive Timer | LockableServiceSupport > | mq.broker.LockableServiceSupport 143 | 73 - activemq-osgi - 5.15.6 | > broker, no longer able to keep the exclusive lock so giving up being a > master > 2019-02-27T16:51:05,909 | INFO | KeepAlive Timer | BrokerService > | he.activemq.broker.BrokerService 836 | 73 - activemq-osgi - 5.15.6 | > Apache ActiveMQ 5.15.6 (broker, amq2) is shutting down > > It doesn't say why it could no longer keep the lock, but anyways, the > bigger issue is that after stopping, it does not restart to retry acquiring > the lock. > > Is there a configuration I'm missing? The code in LockableServiceSupport > actually requests a restart, but where is that re-start done? > > Thanks for any insight > - Martin > >
