I tried but was unable to re-create the error so for now no closer to finding
the cause or a solution.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
thanks for the reply, only db.data was deleted (renamed in fact).
The locks work in testing when stopping/killing/switching off the master
instance of ActiveMQ and the slave takes over and the same when going back.
I'll need to see if I can have the NFS share failing on both servers at the
On Wed, Apr 4, 2018 at 9:18 AM, gbrown wrote:
> We had a short outage on the network and once the this came back both
> instances in our master / slave setup were up and connectable. Once this
> was
> discovered when messages on queues were not browsable or able to be
>