You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Karl Pauls (JIRA)" <ji...@apache.org> on 2017/02/27 12:27:45 UTC
[jira] [Resolved] (FELIX-5566) Stop/update/refresh/start bundles
when updating through the webconsole for faster turnaround
[ https://issues.apache.org/jira/browse/FELIX-5566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Karl Pauls resolved FELIX-5566.
-------------------------------
Resolution: Fixed
Fix Version/s: webconsole-4.3.2
I committed support for this in r1784546.
Furthermore, I deployed a new SNAPSHOT version with the fix - hence, you should be able to test this by locally installing version 4.3.1-SNAPSHOT.
I think this should work - hence, I'm resolving this issue. Please close this issue if it works for you (and feel free to reopen it if something is broken).
> Stop/update/refresh/start bundles when updating through the webconsole for faster turnaround
> --------------------------------------------------------------------------------------------
>
> Key: FELIX-5566
> URL: https://issues.apache.org/jira/browse/FELIX-5566
> Project: Felix
> Issue Type: Improvement
> Components: Web Console
> Affects Versions: webconsole-4.2.18
> Reporter: Alexander Klimetschek
> Assignee: Karl Pauls
> Fix For: webconsole-4.3.2
>
>
> Currently the webconsole (4.2.18) when updating a bundle through the UI/HTTP API will update the bundle and then (optionally) issue a package refresh, leading to 2 restarts of the bundle in question.
> When a bundle has many dependents, and many components/services are involved, that early restart interferes with currently shutting down components that will start again (in our case up to 45 times!).
> Apparently it might be more efficient to do stop the bundle first, then update, refresh and start.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)