Is it common that an activemq broker might give up its NFS v4 lock w/o
logging any sort of message? I've got two brokers that logged this:
broker-a which held the log:
2016-03-17 15:01:51,113 [yMonitor Worker] WARN Transport
- Transport Connection to: tcp://104.232.16.4:62269 failed:
org.apache.activemq.transport.InactivityIOException: Channel was inactive
for too (>30000) long: tcp://xxx.xxx.xxx.xxx:62269
2016-03-18 00:05:22,751 [KeepAlive Timer] INFO LockFile
- Lock file /var/log/activemq/activemq-data/amq-dev-1/lock, locked at
Thu Mar 17 13:38:33 PDT 2016, has been modified at Fri Mar 18 00:02:15 PDT
2016
2016-03-18 00:05:22,758 [KeepAlive Timer] ERROR LockableServiceSupport
- amq-dev-1, no longer able to keep the exclusive lock so giving up
being a master
2016-03-18 00:05:22,761 [KeepAlive Timer] INFO BrokerService
- Apache ActiveMQ 5.13.2 (amq-dev-1, ID:cluster-51079-1458247119790-1:1)
is shutting down
broker-b which appeared to steal the lock:
2016-03-17 13:38:52,680 [JMX connector ] INFO ManagementContext
- JMX consoles can connect to
service:jmx:rmi://localhost:2020/jndi/rmi://localhost:2020/jmxrmi
2016-03-18 00:02:23,593 [erSimpleAppMain] INFO MessageDatabase
- KahaDB is version 6
2016-03-18 00:02:23,762 [erSimpleAppMain] INFO MessageDatabase
- Recovering from the journal @1:63912
2016-03-18 00:02:24,043 [erSimpleAppMain] INFO MessageDatabase
- Recovery replayed 7130 operations from the journal in 0.296 seconds.
2016-03-18 00:02:24,058 [erSimpleAppMain] INFO PListStoreImpl
- PListStore:[/var/log/activemq/activemq-data/amq-dev-1/tmp_storage]
started
