Jonathan Anstey created KARAF-2418:
--------------------------------------
Summary: Minimal distro hanging on startup
Key: KARAF-2418
URL: https://issues.apache.org/jira/browse/KARAF-2418
Project: Karaf
Issue Type: Bug
Affects Versions: 2.4.0
Environment: apache-karaf-2.4.0-SNAPSHOT-minimal.tar.gz
Reporter: Jonathan Anstey
Attachments: KARAF-2418.patch
When running ./bin/karaf on the karaf-2.x branch, the console never appears.
The regular distro starts up fine. In the logs I can see exceptions for many
bundles like:
{code}
2013-07-29 15:36:10,377 | ERROR | FelixStartLevel | BlueprintContainerImpl
| container.BlueprintContainerImpl 394 | 9 -
org.apache.aries.blueprint.core - 1.1.1.SNAPSHOT | Unable to start blueprint
container for bundle org.apache.karaf.features.command
java.lang.NoClassDefFoundError: org/apache/xerces/dom/DeferredElementNSImpl
at org.apache.xerces.dom.DeferredDocumentImpl.getNodeObject(Unknown
Source)[:]
at
org.apache.xerces.dom.DeferredDocumentImpl.synchronizeChildren(Unknown
Source)[:]
at org.apache.xerces.dom.ParentNode.getChildNodes(Unknown Source)[:]
at
org.apache.aries.blueprint.parser.Parser.findNamespaces(Parser.java:262)[9:org.apache.aries.blueprint.core:1.1.1.SNAPSHOT]
at
org.apache.aries.blueprint.parser.Parser.getNamespaces(Parser.java:230)[9:org.apache.aries.blueprint.core:1.1.1.SNAPSHOT]
at
org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:287)[9:org.apache.aries.blueprint.core:1.1.1.SNAPSHOT]
at
org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:261)[9:org.apache.aries.blueprint.core:1.1.1.SNAPSHOT]
at
org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:264)[9:org.apache.aries.blueprint.core:1.1.1.SNAPSHOT]
at
org.apache.aries.blueprint.container.BlueprintExtender.modifiedBundle(BlueprintExtender.java:227)[9:org.apache.aries.blueprint.core:1.1.1.SNAPSHOT]
at
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:500)[13:org.apache.aries.util:1.1.0]
at
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:433)[13:org.apache.aries.util:1.1.0]
at
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$AbstractTracked.track(BundleHookBundleTracker.java:725)[13:org.apache.aries.util:1.1.0]
at
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.bundleChanged(BundleHookBundleTracker.java:463)[13:org.apache.aries.util:1.1.0]
at
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$BundleEventHook.event(BundleHookBundleTracker.java:422)[13:org.apache.aries.util:1.1.0]
at
org.apache.felix.framework.util.SecureAction.invokeBundleEventHook(SecureAction.java:1103)[org.apache.felix.framework-4.0.3.jar:]
at
org.apache.felix.framework.util.EventDispatcher.createWhitelistFromHooks(EventDispatcher.java:695)[org.apache.felix.framework-4.0.3.jar:]
at
org.apache.felix.framework.util.EventDispatcher.fireBundleEvent(EventDispatcher.java:483)[org.apache.felix.framework-4.0.3.jar:]
at
org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4244)[org.apache.felix.framework-4.0.3.jar:]
at
org.apache.felix.framework.Felix.startBundle(Felix.java:1923)[org.apache.felix.framework-4.0.3.jar:]
at
org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1191)[org.apache.felix.framework-4.0.3.jar:]
at
org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:295)[org.apache.felix.framework-4.0.3.jar:]
at java.lang.Thread.run(Thread.java:722)[:1.7.0_11]
{code}
It appears that endorsing jaxp (like the one included in the regular kit)
solves the hang issue. Will attach a patch shortly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
