[
https://issues.apache.org/jira/browse/AMQ-4645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13783838#comment-13783838
]
Joe Luo commented on AMQ-4645:
------------------------------
The subject title of this JIRA is a bit misleading and it should be "The
lease-database-locker does not work properly slave broker system clock is ahead
of Database server". So it was a problem only when the slave broker system
clock is ahead of the Database server but not behind.
> The lease-database-locker does not work properly slave broker ssytem clock is
> behind Database server
> ----------------------------------------------------------------------------------------------------
>
> Key: AMQ-4645
> URL: https://issues.apache.org/jira/browse/AMQ-4645
> Project: ActiveMQ
> Issue Type: Bug
> Components: Message Store
> Affects Versions: 5.8.0
> Environment: jdbc master slave
> Reporter: Gary Tully
> Assignee: Gary Tully
> Labels: clock, jdbc, lease, masterSlave
> Fix For: 5.9.0
>
>
> The lease locker can adjust the lease duration based on the DB current time
> but this only works if the broker is ahead of the Db.
> If the broker is behind, it will always obtain a lease due to incorrect
> adjustment.
> If the clocks are in sync there is no issue.{code}
> <persistenceAdapter>
> <jdbcPersistenceAdapter dataSource="#oracle-ds"
> lockKeepAlivePeriod="5000">
> <locker>
> <lease-database-locker lockAcquireSleepInterval="10000"/>
> </locker>
> </jdbcPersistenceAdapter>
> </persistenceAdapter>{code}
> The problem is that the negative diff is being treated as a positive diff.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
