Features repository url not available during startup
----------------------------------------------------
Key: SMX4-389
URL: https://issues.apache.org/activemq/browse/SMX4-389
Project: ServiceMix 4
Issue Type: Bug
Affects Versions: specs-1.2.0
Reporter: Gert Vanthienen
Assignee: Gert Vanthienen
Fix For: 4.1.0
When starting the container, you sometimes get
{noformat}
[pool-2-thread-1] ERROR
org.apache.geronimo.blueprint.container.BlueprintContainerImpl - Unable to
start blueprint container for bundle org.apache.felix.karaf.features.core
org.osgi.service.blueprint.container.ComponentDefinitionException: Unable to
intialize bean featuresService
at
org.apache.geronimo.blueprint.container.BeanRecipe.internalCreate(BeanRecipe.java:519)
at
org.apache.geronimo.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:64)
at
org.apache.geronimo.blueprint.container.BlueprintRepository.createInstances(BlueprintRepository.java:212)
at
org.apache.geronimo.blueprint.container.BlueprintRepository.createAll(BlueprintRepository.java:140)
at
org.apache.geronimo.blueprint.container.BlueprintContainerImpl.instantiateEagerComponents(BlueprintContainerImpl.java:603)
at
org.apache.geronimo.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:310)
at
org.apache.geronimo.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:211)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:65)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:168)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.RuntimeException: URL
[mvn:org.apache.camel.karaf/features/2.1-SNAPSHOT/xml/features] could not be
resolved.
at org.ops4j.pax.url.mvn.internal.Connection.getInputStream(Connection.java:195)
at
org.apache.felix.karaf.features.internal.RepositoryImpl.load(RepositoryImpl.java:89)
at
org.apache.felix.karaf.features.internal.FeaturesServiceImpl.internalAddRepository(FeaturesServiceImpl.java:153)
at
org.apache.felix.karaf.features.internal.FeaturesServiceImpl.start(FeaturesServiceImpl.java:409)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.geronimo.blueprint.utils.ReflectionUtils.invoke(ReflectionUtils.java:206)
at
org.apache.geronimo.blueprint.container.BeanRecipe.invoke(BeanRecipe.java:639)
at
org.apache.geronimo.blueprint.container.BeanRecipe.internalCreate(BeanRecipe.java:517)
... 14 more
{noformat}
This is caused by the FeaturesService starting before the ConfigAdmin
configuration for pax url mvn: has been loaded.
Cfr. https://issues.apache.org/jira/browse/FELIX-1628 and
https://issues.apache.org/jira/browse/FELIX-1626
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
