[jira] [Resolved] (AMQ-4645) The lease-database-locker does not work properly slave broker ssytem clock is behind Database server

["Gary Tully (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AMQ-4645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Tully resolved AMQ-4645.
-----------------------------

    Resolution: Fixed

diff now applied correctly. Additional tests to validate
                
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira