You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2012/08/20 14:38:38 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13437823#comment-13437823 ]
Bertrand Delacretaz commented on SLING-2566:
--------------------------------------------
Created SLING-2567 for the PABundleRefresher.isInstallerBundleAffected() method issue.
> 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
> Fix For: Installer Core 3.3.10
>
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira