[ 
https://issues.apache.org/jira/browse/ARIES-1444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14985409#comment-14985409
 ] 

Bas commented on ARIES-1444:
----------------------------

We use karaf 4 with equinox so I think it is part of equinox v3.10.2. I tried 
to reproduce the problem but I was unable to so it might just be a bug in this 
version.

It is not part of the 400 subsystems case, I can reproduce it by installing one 
feature subsystem. Then restarting the container and trying to install a second 
one. Both features contain an application subsystem. I tried to create a 
pax-exam case for it but was unable to reproduce it. I think the resolver is 
continuously telling itself there is a feature that exports a package which is 
also part of a uses of one of its imports. I don't see an issue in that but it 
seems to retry because of that.

So it occurs after a restart when trying to install an additional feature. The 
feature it complains about is the feature that is already installed.

> Subsystem does not install because feature subsystem exports all constituents
> -----------------------------------------------------------------------------
>
>                 Key: ARIES-1444
>                 URL: https://issues.apache.org/jira/browse/ARIES-1444
>             Project: Aries
>          Issue Type: Bug
>          Components: Subsystem
>    Affects Versions: subsystem-core-2.0.4
>         Environment: karaf
>            Reporter: Bas
>
> The resolver will try endlessly to resolve the situation presented to it. You 
> do have to restart the subsystem core bundle before this happens because 
> after that the feature exports all constituent capabilities.
>  
> While debugging it shows the following messages: 
> org.osgi.service.resolver.ResolutionException: Uses constraint violation. 
> Unable to resolve resource 
> nl.capesystemsintegration.testcu.bus.testms.container-infra 
> [org.apache.aries.subsystem.core.internal.BasicSubsystem@73ed4f] because it 
> exports package 'net.sf.saxon.sxpath' and is also exposed to it from resource 
> org.apache.servicemix.bundles.saxon [osgi.identity; 
> osgi.identity="org.apache.servicemix.bundles.saxon"; type="osgi.bundle"; 
> version:Version="9.4.0.7_1"] via the following dependency chain:
>   nl.capesystemsintegration.testcu.bus.testms.container-infra 
> [org.apache.aries.subsystem.core.internal.BasicSubsystem@73ed4f]
>     import: 
> (&(osgi.wiring.package=net.sf.saxon.trans)(&(version>=9.4.0)(!(version>=10.0.0))))
>      |
>     export: osgi.wiring.package: net.sf.saxon.trans; uses:=net.sf.saxon.sxpath
>     export: osgi.wiring.package=net.sf.saxon.sxpath
>   org.apache.servicemix.bundles.saxon [osgi.identity; 
> osgi.identity="org.apache.servicemix.bundles.saxon"; type="osgi.bundle"; 
> version:Version="9.4.0.7_1"]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to