[
https://issues.apache.org/jira/browse/ARIES-1428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Ross resolved ARIES-1428.
------------------------------
Resolution: Fixed
http://svn.apache.org/viewvc?rev=1707431&view=rev
> org.osgi.framework.BundleException: Could not resolve module: <module> Bundle
> was filtered by a resolver hook.
> --------------------------------------------------------------------------------------------------------------
>
> Key: ARIES-1428
> URL: https://issues.apache.org/jira/browse/ARIES-1428
> Project: Aries
> Issue Type: Bug
> Components: Subsystem
> Affects Versions: subsystem-2.0.4
> Reporter: John Ross
> Assignee: John Ross
> Fix For: subsystem-2.0.6
>
>
> This exception may occur during a small window of time between the
> registration of the resolver hook and initialization of the root subsystem
> while the implementation bundle is being activated.
> ARIES-1392 introduced the need to prevent bundles that are part of a
> subsystem installation from resolving until the installation is complete. An
> assumption made was that a check to see if the bundle was referenced by any
> subsystems was sufficient. This is not the case because during the small
> window of time mentioned previously, the resolver hook will think that no
> bundles are associated with any subsystems. If a bundle undergoes a
> resolution attempt during this period, it will fail.
> The solution is to ensure that the resolver hook will only prevent bundles
> not referenced by any subsystems from resolving on the same thread as the
> subsystem installation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)