You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2016/12/01 09:19:59 UTC
[jira] [Commented] (KARAF-4739) Rebooting Karaf can cause some
bundles to not resolve anymore
[ https://issues.apache.org/jira/browse/KARAF-4739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15711437#comment-15711437 ]
ASF subversion and git services commented on KARAF-4739:
--------------------------------------------------------
Commit 1369d9f4e0bb53d62aa36bb9f199fab594473e86 in karaf's branch refs/heads/karaf-4.0.x from [~gnt]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=1369d9f ]
KARAF-4739 Fix computation of snapshots crc for fragments
> Rebooting Karaf can cause some bundles to not resolve anymore
> -------------------------------------------------------------
>
> Key: KARAF-4739
> URL: https://issues.apache.org/jira/browse/KARAF-4739
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
> Affects Versions: 4.0.7
> Reporter: Guillaume Nodet
> Assignee: Guillaume Nodet
> Fix For: 4.1.0
>
>
> The nice thing of the features service is that is uses the resolver to compute a working solution, then applies it.
> However, after a reboot, the feature service does not have any say in the resolution done by the framework and thus, the framework may fail to resolve the bundles properly.
> This mostly happen on felix I think, as afaik, equinox does keep the bundle wiring.
> One work around would be to have the features service store the wiring and re-apply it during the boot. Another one may be to completely re-run the resolution after a reboot while the features service bundle is starting.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)