You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Holly Cummins (JIRA)" <ji...@apache.org> on 2012/05/28 16:18:24 UTC
[jira] [Resolved] (ARIES-858) Build break: Blueprint container
sometimes fails to start, causing application test failures
[ https://issues.apache.org/jira/browse/ARIES-858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Holly Cummins resolved ARIES-858.
---------------------------------
Resolution: Fixed
I've reverted those concurrency changes (http://www.svnsearch.org/svnsearch/repos/ASF/search?p=/aries/trunk/blueprint/blueprint-core/src/main/java/org/apache/aries/blueprint/namespace/NamespaceHandlerRegistryImpl.java&rev=1341258&path=%2Faries) to fix the test failures.
> Build break: Blueprint container sometimes fails to start, causing application test failures
> --------------------------------------------------------------------------------------------
>
> Key: ARIES-858
> URL: https://issues.apache.org/jira/browse/ARIES-858
> Project: Aries
> Issue Type: Bug
> Components: Blueprint
> Reporter: Holly Cummins
> Assignee: Holly Cummins
> Priority: Blocker
>
> Since build ARES-1461, we're seeing around 13 failures, although the exact tests which fail varies slightly. Usually there's a failure in org.apache.aries.application.runtime.itests.IsolatedRuntimeTest and org.apache.aries.application.runtime.itests.OBRResolverAdvancedTest.
> The root cause seems to be an NPE in NamespaceHandlerRegistryImpl:
> [Blueprint Extender: 2] ERROR org.apache.aries.blueprint.container.BlueprintContainerImpl - Unable to start blueprint container for bundle org.apache.aries.application.default.local.platform
> java.lang.NullPointerException
> at java.util.LinkedList.remove(LinkedList.java:792)
> at java.util.LinkedList.remove(LinkedList.java:226)
> at org.apache.aries.blueprint.namespace.NamespaceHandlerRegistryImpl$LRUMap.get(NamespaceHandlerRegistryImpl.java:682)
> at org.apache.aries.blueprint.namespace.NamespaceHandlerRegistryImpl.getSchema(NamespaceHandlerRegistryImpl.java:243)
> at org.apache.aries.blueprint.namespace.NamespaceHandlerRegistryImpl.access$200(NamespaceHandlerRegistryImpl.java:74)
> at org.apache.aries.blueprint.namespace.NamespaceHandlerRegistryImpl$NamespaceHandlerSetImpl.getSchema(NamespaceHandlerRegistryImpl.java:502)
> at org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:291)
> at org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:242)
> This issue seems to have been introduced in revision 1341258 on 22.05.2012 01:12:57, "Improve concurrency in the namespace registry".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira