You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Karl Pauls (Jira)" <ji...@apache.org> on 2020/12/11 21:07:00 UTC

[jira] [Updated] (FELIX-6163) ServiceTracker should not use System.currentTimeMillis() to check timeouts

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

Karl Pauls updated FELIX-6163:
------------------------------
    Fix Version/s:     (was: framework-6.0.4)
                   framework-7.0.0

> ServiceTracker should not use System.currentTimeMillis() to check timeouts
> --------------------------------------------------------------------------
>
>                 Key: FELIX-6163
>                 URL: https://issues.apache.org/jira/browse/FELIX-6163
>             Project: Felix
>          Issue Type: Bug
>          Components: Framework
>    Affects Versions: framework-6.0.3
>            Reporter: Tobias Gunkel
>            Assignee: Karl Pauls
>            Priority: Major
>             Fix For: framework-7.0.0
>
>
> ServiceTracker uses System.currentTimeMillis() to check timeouts in waitForService().
> If the system time changes either:
>  * the timeout might occur to soon - if the time was set to the future
>  * the timeout might not occur in a reasonable time - if the time was set to the past
> Instead of System.currentTimeMillis() the system tick based System.nanoTime() should be used as it does not to change after the system time is changed.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)