You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2010/09/14 08:33:34 UTC

[jira] Resolved: (SLING-1773) Possible to store newly install bundle digests into bundle-digests.properties immediately after the bundle is installed successfully

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

Carsten Ziegeler resolved SLING-1773.
-------------------------------------

         Assignee: Carsten Ziegeler
    Fix Version/s: OSGi Installer 3.0.0
       Resolution: Fixed

With SLING-1737 we now have a better state management which ensures that once a bundle is installed it is immediately marked as installed. The extra saving of digests has been completly removed.

> Possible to store newly install bundle digests into bundle-digests.properties immediately after the bundle is installed successfully
> ------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SLING-1773
>                 URL: https://issues.apache.org/jira/browse/SLING-1773
>             Project: Sling
>          Issue Type: Improvement
>          Components: Installer
>    Affects Versions: JCR Installer 3.0.0
>         Environment: CQ5.3
>            Reporter: zhangchunlong
>            Assignee: Carsten Ziegeler
>            Priority: Minor
>             Fix For: OSGi Installer 3.0.0
>
>
> Bundle slinginstall:org.apache.sling.osgi.installer-3.0.0-R900409.jar in CQ5.3 only try to store the bundle digests into bundle-digests.properties when the server is shutting down. In case some bundles are installed and the server is not shutdown properly. eg. crash, being killed, next time when CQ5.3 starts, will try to re-install those bundles and leave the bundle status as "installed". It might be good to store such information immediately after any bundle is being installed successfully if possible.
> To reproduce the issue:
> 1. create some test bundle
> 2. start the CQ5.3 instance, install the test bundle into some /install folder.
> 3. kill the CQ5.3 instance.
> 4. start the CQ5.3 instance again.
> 5. from the crx-quickstart/logs/error.log, could see the test bundle is being installed again.
> 6. from Felix console, the test bundle status is "installed".

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.