You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Guillaume Nodet (JIRA)" <ji...@apache.org> on 2015/12/03 16:15:11 UTC

[jira] [Commented] (KARAF-3973) Bundles refresh doesn't work (bundles not resolved)

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

Guillaume Nodet commented on KARAF-3973:
----------------------------------------

You should provide the bundle headers and the resolution exception from the log so that it can be investigated.

> Bundles refresh doesn't work (bundles not resolved)
> ---------------------------------------------------
>
>                 Key: KARAF-3973
>                 URL: https://issues.apache.org/jira/browse/KARAF-3973
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-core
>    Affects Versions: 4.0.1
>            Reporter: Amichai Rothman
>            Priority: Critical
>
> I have a bunch of bundles copied into the deploy folder of a fresh karaf 4.0.1 installation. The first time karaf runs, the bundles are not properly resolved, and apparently this has to do with the order in which they are loaded, i.e. if A depends on B and A is loaded first, then when B is loaded it is properly resolved but A never gets resolved. running the refresh command from console does not help either. However, if karaf itself is restarted, then everything is resolved and activated with no problem.
> In Karaf up to 3.0.3 this was not an issue - the moment B was loaded, even on the first time Karaf is run, A would automatically get resolved/activated as well. on 3.0.4 I get a deadlock on startup, so can't really tell if it works (see KARAF-3941). on 4.0.0 I haven't tried. 4.0.1 is the current reported issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)