[
https://issues.apache.org/jira/browse/KARAF-3973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15594282#comment-15594282
]
Guillaume Nodet commented on KARAF-3973:
----------------------------------------
Such problems are difficult to investigate as they depend on list of bundles
deployed, their order, etc...
One of the stack trace above comes from the fact that you have 2 versions of
the servlet api deployed: [osgi.identity; osgi.identity="javax.servlet";
type="osgi.bundle"; version:Version="3.0.0.v201112011016"] and [osgi.identity;
osgi.identity="javax.servlet-api"; type="osgi.bundle"; version:Version="3.1.0"].
I would suggest that you remove the references to one of the bundle above from
your features, or that you blacklist it.
To blacklist a bundle, you need to add the bundle url to a
{{etc/blacklisted.properties}} file, or if you use the karaf maven plugin, add
it to the configuration in the pom:
{code}
<blacklistedBundles>
<bundle>mvn:org.apache.camel.karaf/camel-karaf-commands/2.18.0-SNAPSHOT</bundle>
</blacklistedBundles>
{code}
But I'm not really sure it will be sufficient. Again, if you want more, you'll
have to provide a way to actually reproduce the problem.
> 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)
