Mailing-List: contact dev-help@aries.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@aries.apache.org
Date: Mon, 15 Jul 2013 20:06:48 +0000 (UTC)
From: "John Ross (JIRA)" <jira@apache.org>
To: dev@aries.apache.org
Message-ID: <JIRA.12657319.1373574239587.52660.1373918808475@arcas>
In-Reply-To: <JIRA.12657319.1373574239587@arcas>
References: <JIRA.12657319.1373574239587@arcas>
Subject: [jira] [Resolved] (ARIES-1089) Handlers map in
 NamespaceHandlerSetImpl is unsafe.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/ARIES-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Ross resolved ARIES-1089.
------------------------------

    Resolution: Fixed

Fixed in http://svn.apache.org/viewvc?view=revision&revision=1503441.
                
> Handlers map in NamespaceHandlerSetImpl is unsafe.
> --------------------------------------------------
>
>                 Key: ARIES-1089
>                 URL: https://issues.apache.org/jira/browse/ARIES-1089
>             Project: Aries
>          Issue Type: Bug
>          Components: Blueprint
>            Reporter: John Ross
>            Assignee: John Ross
>
> The NamespaceHandlerSetImpl class uses an unprotected map to store handlers. The map is accessible to multiple threads. For example, the thread delivering the NamespaceHandler service registration event will store the handler in the map and eventually call BlueprintContainerImpl.schedule, which spawns off another thread that will look for a handler in the map.
> We appear to be encountering a visibility issue where the org.apache.aries.application.resolver.obr bundle will never activate because blueprint thinks the required namespace handler is not available. However, the logs clearly show the namespace handler being registered anywhere from a millisecond to one or two seconds previously.
> Would there be any objections to using a ConcurrentHashMap?

--
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