[jira] [Created] (ARIES-1206) Aries Blueprint does not startup properly - timeouts for JAAS namespace and KeystoreManager

["Martin Lichtin (JIRA)" <ji...@apache.org>]

Martin Lichtin created ARIES-1206:
-------------------------------------

             Summary: Aries Blueprint does not startup properly - timeouts for JAAS namespace and KeystoreManager
                 Key: ARIES-1206
                 URL: https://issues.apache.org/jira/browse/ARIES-1206
             Project: Aries
          Issue Type: Bug
          Components: Blueprint
         Environment: Karaf 2.3.4 startup
            Reporter: Martin Lichtin


Aries startup fails with following logs emitted:

{noformat}
2014-06-09 20:37:45,829 | INFO  | FelixStartLevel          | BlueprintContainerImpl           | container.BlueprintContainerImpl  352 | 7 - org.apache.aries.blueprint.core - 1.4.0 | Bundle org.apache.karaf.management.server is waiting for dependencies [(objectClass=org.apache.karaf.jaas.config.KeystoreManager)]
2014-06-09 20:37:45,957 | INFO  | FelixStartLevel          | BlueprintContainerImpl           | container.BlueprintContainerImpl  315 | 7 - org.apache.aries.blueprint.core - 1.4.0 | Bundle org.apache.karaf.jaas.modules is waiting for namespace handlers [http://karaf.apache.org/xmlns/jaas/v1.0.0]
2014-06-09 20:42:45,828 | ERROR | Blueprint Extender: 2    | BlueprintContainerImpl           | ntainer.BlueprintContainerImpl$1  340 | 7 - org.apache.aries.blueprint.core - 1.4.0 | Unable to start blueprint container for bundle org.apache.karaf.management.server due to unresolved dependencies [(objectClass=org.apache.karaf.jaas.config.KeystoreManager)]
java.util.concurrent.TimeoutException
	at org.apache.aries.blueprint.container.BlueprintContainerImpl$1.run(BlueprintContainerImpl.java:336)[7:org.apache.aries.blueprint.core:1.4.0]
	at org.apache.aries.blueprint.utils.threading.impl.DiscardableRunnable.run(DiscardableRunnable.java:48)[7:org.apache.aries.blueprint.core:1.4.0]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)[:1.7.0_13]
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)[:1.7.0_13]
	at java.util.concurrent.FutureTask.run(FutureTask.java:166)[:1.7.0_13]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)[:1.7.0_13]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)[:1.7.0_13]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)[:1.7.0_13]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)[:1.7.0_13]
	at java.lang.Thread.run(Thread.java:722)[:1.7.0_13]
{noformat}

Afaics, such a timeout should never occur, as all the information _should_ be available in Karaf's local M2 repository.



--
This message was sent by Atlassian JIRA
(v6.2#6252)