aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wouter Bancken (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (ARIES-1443) After a restart the capabilities of a subsystem have changed (seem correct) before the restart they seem wrong
Date Tue, 26 Jul 2016 16:15:20 GMT

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

Wouter Bancken edited comment on ARIES-1443 at 7/26/16 4:14 PM:
----------------------------------------------------------------

The commit done for this issue seems to have broken the deployment of our application. If
I use a version before commit 74c0437de06f34321909a6132a7f2be163b2f6d5, our deployment works.

Before commit 74c0437de06f34321909a6132a7f2be163b2f6d5, the getCapabilities method only returned
the identity capability for our subsystems. Now it returns the union of all capabilities of
the subsystems content (as intended by the commit).

Our setup contains two feature subsystems. The errors arise during the installation of the
second subsystem and are all similar to the following:

DEBUG: Candidate permutation failed due to a conflict between an export and import; will try
another if possible. (org.osgi.service.resolver.ResolutionException: Uses constraint violation.
Unable to resolve resource org.ops4j.pax.web.pax-web-jetty-bundle [195.0] because it exports
package 'org.apache.xbean.finder.archive' and is also exposed to it from resource org.apache.xbean.finder
[98.0] via the following dependency chain:

  org.ops4j.pax.web.pax-web-jetty-bundle [195.0]
    import: (osgi.wiring.package=org.apache.xbean.finder)
     |
    export: osgi.wiring.package: org.apache.xbean.finder; uses:=org.apache.xbean.finder.archive
    export: osgi.wiring.package=org.apache.xbean.finder.archive
  org.apache.xbean.finder [98.0])

This is especially weird since pax-web-jetty-bundle does not expose the org.apache.xbean.finder.archive
package (see attached Jar). Both pax-web-jetty-bundle and org.apache.xbean.finder are only
present in the first subsystem. The issue occurs for multiple bundles with different packages

The exposure of the capabilities seems to interfere with the bundle wiring.


was (Author: wouter bancken):
The commit done for this issue seems to have broken the deployment of our application. If
I use a version before commit 74c0437de06f34321909a6132a7f2be163b2f6d5, our deployment works.

Before commit 74c0437de06f34321909a6132a7f2be163b2f6d5, the getCapabilities method only returned
the identity capability for our subsystems. Now it returns the union of all capabilities of
the subsystems content (as intended by the commit).

Our setup contains two feature subsystems. The errors arise during the installation of the
second subsystem and are all similar to the following:

DEBUG: Candidate permutation failed due to a conflict between an export and import; will try
another if possible. (org.osgi.service.resolver.ResolutionException: Uses constraint violation.
Unable to resolve resource org.ops4j.pax.web.pax-web-jetty-bundle [195.0] because it exports
package 'org.apache.xbean.finder.archive' and is also exposed to it from resource org.apache.xbean.finder
[98.0] via the following dependency chain:

  org.ops4j.pax.web.pax-web-jetty-bundle [195.0]
    import: (osgi.wiring.package=org.apache.xbean.finder)
     |
    export: osgi.wiring.package: org.apache.xbean.finder; uses:=org.apache.xbean.finder.archive
    export: osgi.wiring.package=org.apache.xbean.finder.archive
  org.apache.xbean.finder [98.0])

This is especially weird since pax-web-jetty-bundle does not expose the org.apache.xbean.finder.archive
package (see attached Jar). Both pax-web-jetty-bundle and org.apache.xbean.finder are only
present in the first subsystem. 

The exposure of the capabilities seems to interfere with the bundle wiring.

> After a restart the capabilities of a subsystem have changed (seem correct) before the
restart they seem wrong
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: ARIES-1443
>                 URL: https://issues.apache.org/jira/browse/ARIES-1443
>             Project: Aries
>          Issue Type: Bug
>          Components: Subsystem
>    Affects Versions: subsystem-2.0.6, subsystem-2.0.8
>         Environment: karaf pax-exam
>            Reporter: Bas
>            Assignee: John Ross
>              Labels: test-patch
>             Fix For: subsystem-2.1.0
>
>         Attachments: CapabilitiesDifferOnRestart.java.patch, pax-web-jetty-bundle-4.2.5.jar
>
>
> A feature subsystem should export all capabilities of its constituents and it does not
do that after a fresh install. After a restart of the subsystem core bundle it will export
all the capabilities. 
> These seems to be a difference in parsing the capabilities of a persisted subsystem and
a new subsystem.



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

Mime
View raw message