You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "clebert suconic (JIRA)" <ji...@apache.org> on 2019/01/18 02:21:05 UTC

[jira] [Closed] (ARTEMIS-2110) JDBC LeaseLocker repeated renew or renew after aquire can fail in error

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

clebert suconic closed ARTEMIS-2110.
------------------------------------

> JDBC LeaseLocker repeated renew or renew after aquire can fail in error
> -----------------------------------------------------------------------
>
>                 Key: ARTEMIS-2110
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2110
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 2.6.3
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>            Priority: Minor
>             Fix For: 2.7.0, 2.6.4
>
>
> There is an intermittent failure in:
> org.apache.activemq.artemis.core.server.impl.jdbc.JdbcLeaseLockTest#shouldRenewAcquiredLock
> (seems to block pr ci, and reproduced for me 20% of the time)
> if the db currentTime has not moved on, using the same lease time results in a failure. A renew immediately after acquiring the lock is a sensible pattern to verify the aquire. 
>  
> The lock renew needs >= in place or > on the WHERE clause to allow an 'identity' lease to succeed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)