[
https://issues.apache.org/jira/browse/SLING-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13467782#comment-13467782
]
Bertrand Delacretaz commented on SLING-2566:
--------------------------------------------
IMO the cleanest would be to interrupt the background thread after a timeout of
a few seconds, to make sure it's not lingering around. But if we don't do that
right now, WONTFIX is fine, and we can always reopen later if needed.
> 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.4.0
>
> 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
