You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@activemq.apache.org by andrewhelicopter <an...@petcircle.com.au> on 2015/07/02 01:09:15 UTC

Re: kahadb lock in logs

Replying to my own post now months later.

We successfully had 5.11.0 running for over 136 days until we decided to do
some maintenance and reboot the server this morning.

Now first problem, is again we couldn't get the lock. The consumers would
connect but could not enqueue messages. I will attach the log file.
activemq.log-old
<http://activemq.2283324.n4.nabble.com/file/n4698488/activemq.log-old>  

So I moved the old directory then extracted a fresh copy from
apache-activemq-5.11.0-bin.tar.gz and tried to start. Again there was a
problem attaining lock. Deleted the lock file and the suddenly the
connections could send messages !

The problem I'm seeing now is that the broker tries to start another service
but cannot due to the existing process.
activemq.log-new
<http://activemq.2283324.n4.nabble.com/file/n4698488/activemq.log-new>  

Is this a bug or what ?



--
View this message in context: http://activemq.2283324.n4.nabble.com/kahadb-lock-in-logs-tp4691746p4698488.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.