karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KARAF-4739) Rebooting Karaf can cause some bundles to not resolve anymore
Date Wed, 05 Oct 2016 12:23:20 GMT

    [ https://issues.apache.org/jira/browse/KARAF-4739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15548551#comment-15548551
] 

ASF subversion and git services commented on KARAF-4739:
--------------------------------------------------------

Commit 4d8760e3bf474c123d82f6e4fb315b57aa5cc27b in karaf's branch refs/heads/master from [~gnt]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=4d8760e ]

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

Mime
View raw message