activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Tully <>
Subject Re: Lease based locker fails as slave starts when master is still up
Date Mon, 17 Dec 2012 16:35:52 GMT
that does seem odd.
Are the system clocks in sync on both machines?

It would be interesting to get db logs to see the exact sequence of
statements with values.
The idea is that a lease update would fail if the slave takes over, but
that does not seem to be the case on your master.
It appears that the slave is checking for expiry about the same time that
the master should be  updating, so it becomes a master, but in this case
the slave should give up.

Consider using the same timeout values on both the master and slave but it
does look like there is a bug here.

On 13 December 2012 07:10, mandar.wanpal <> wrote:

> lockAcquireSleepInterval


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message