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 2012/10/02 18:03:07 UTC

[jira] [Resolved] (SLING-2566) Installer should interrupt its background thread when deactivated

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

Carsten Ziegeler resolved SLING-2566.
-------------------------------------

    Resolution: Won't Fix

Ok, let's go with wont fix for now :)
                
> Installer should interrupt its background thread when deactivated
> -----------------------------------------------------------------
>
>                 Key: SLING-2566
>                 URL: https://issues.apache.org/jira/browse/SLING-2566
>             Project: Sling
>          Issue Type: Bug
>          Components: Installer
>    Affects Versions: Installer Core 3.3.8
>            Reporter: Bertrand Delacretaz
>            Assignee: Bertrand Delacretaz
>            Priority: Minor
>         Attachments: SLING-2566.patch
>
>
> I'm still fighting some problems in upgrading older versions of our Sling-based system, where many bundles are replaced shortly after startup.
> SLING-2552 and SLING-2556 have helped in some cases, but the PABundleRefresher.isInstallerBundleAffected() method does not seem to detect all cases where a bundles refresh causes the installer bundle to stop.
> I'll attach a patch for the OsgiInstallerImpl to interrupt its background thread when deactivated, and discuss on list.

--
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