[jira] [Resolved] (SLING-7051) Upgrade detection might fail due to file system inaccuracy

["Carsten Ziegeler (JIRA)" <ji...@apache.org>]

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

Carsten Ziegeler resolved SLING-7051.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: Launchpad Base 2.6.24

Fixed in rev 1805260 by simply writing the timestamp file again after a successful startup

> Upgrade detection might fail due to file system inaccuracy
> ----------------------------------------------------------
>
>                 Key: SLING-7051
>                 URL: https://issues.apache.org/jira/browse/SLING-7051
>             Project: Sling
>          Issue Type: Improvement
>          Components: Launchpad
>    Affects Versions: Launchpad Base 2.6.22
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: Launchpad Base 2.6.24
>
>
> The upgrade detection is passed on compared file time stamps with a precise timestamp. If the file system has some inaccuracy it might happen that on a restart, the time stamp of a jar file is detected as newer compared to the previously precise stored timestamp. Which results in detecting the restart as an update. And this in turn starts the same cycle again.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)