aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Ross (JIRA)" <>
Subject [jira] [Resolved] (ARIES-1089) Handlers map in NamespaceHandlerSetImpl is unsafe.
Date Mon, 15 Jul 2013 20:06:48 GMT


John Ross resolved ARIES-1089.

    Resolution: Fixed

Fixed in
> Handlers map in NamespaceHandlerSetImpl is unsafe.
> --------------------------------------------------
>                 Key: ARIES-1089
>                 URL:
>             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:

View raw message