karaf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Cristiano Costantini <cristiano.costant...@gmail.com>
Subject Re: [VOTE] Apache Karaf Cellar 4.0.1 release
Date Fri, 15 Jul 2016 06:56:20 GMT
Hi again,
at first I've tested my application with cellar 4.0.1 and everything seemed
to be working,
but after that, I'm having issues with FeatureServiceImpl and with felix
ResolverImpl and the container randomly fails to start.

After some investigation, I've discovered one potential cause in
camel-hazelcast:

The camel hazelcast feature installs the Hazelcast bundle with version
3.5.2:
karaf@root>feature:info camel-hazelcast
Feature camel-hazelcast 2.16.3
Feature has no configuration
Feature has no configuration files
Feature depends on:
  camel-core 2.16.3
  transaction 0.0.0
Feature contains followed bundles:

mvn:org.apache.servicemix.specs/org.apache.servicemix.specs.scripting-api-1.0/2.5.0
  mvn:com.eclipsesource.minimal-json/minimal-json/0.9.4
  mvn:com.hazelcast/hazelcast/3.5.2
  mvn:com.hazelcast/hazelcast-client/3.5.2
  mvn:org.apache.camel/camel-hazelcast/2.16.3
Feature has no conditionals.


Raising up the felix log level I've discovered that during installation of
the features, the ResolverImpl loops over this:

DEBUG: Candidate permutation failed due to a conflict between imports; will
try another if possible. (Uses constraint violation. Unable to resolve
resource org.apache.camel.camel-hazelcast
[org.apache.camel.camel-hazelcast/2.16.3] because it is exposed to package
'com.hazelcast.config' from resources com.hazelcast [com.hazelcast/3.5.2]
and com.hazelcast [com.hazelcast/3.6.4] via two dependency chains.

Chain 1:
  org.apache.camel.camel-hazelcast [org.apache.camel.camel-hazelcast/2.16.3]
    import:
(&(osgi.wiring.package=com.hazelcast.config)(version>=3.2.0)(!(version>=4.0.0)))
     |
    export: osgi.wiring.package: com.hazelcast.config
  com.hazelcast [com.hazelcast/3.5.2]

Chain 2:
  org.apache.camel.camel-hazelcast [org.apache.camel.camel-hazelcast/2.16.3]
    import:
(&(osgi.wiring.package=com.hazelcast.config)(version>=3.2.0)(!(version>=4.0.0)))
     |
    export: osgi.wiring.package=com.hazelcast.config;
uses:=com.hazelcast.core
  com.hazelcast [com.hazelcast/3.5.2]
    import:
(&(osgi.wiring.package=com.hazelcast.core)(version>=3.6.0)(!(version>=4.0.0)))
     |
    export: osgi.wiring.package=com.hazelcast.core; uses:=com.hazelcast.core
  com.hazelcast [com.hazelcast/3.6.4]
    import:
(&(osgi.wiring.package=com.hazelcast.core)(version>=3.6.0)(!(version>=4.0.0)))
     |
    export: osgi.wiring.package: com.hazelcast.core;
uses:=com.hazelcast.config
    export: osgi.wiring.package=com.hazelcast.config
  com.hazelcast [com.hazelcast/3.6.4])



Anyway I'm still opting up for a +1 (non binding) vote,
and I'm thinking to fix locally the problem by substituting the original
camel-hazelcast feature, with one written by myself which instead of
installing directly the hazelcast bundle, it depends on the cellar's
hazelcast, I'll try with something like:

<feature name="cellar-camel-hazelcast">
    <feature>camel-core</feature>
    <feature>transaction</feature>
    <feature>hazelcast</feature> <!-- this feature is defined in
karaf-cellar-4.0.1 -->

<bundle>mvn:org.apache.servicemix.specs/org.apache.servicemix.specs.scripting-api-1.0/2.5.0</bundle>
    <bundle>mvn:com.eclipsesource.minimal-json/minimal-json/0.9.4</bundle>
    <bundle>mvn:org.apache.camel/camel-hazelcast/2.16.3</bundle>
</feature>


I'll let you know if the problems are resolved.

Thank you,
Cristiano


P.S. I don't think it is just a problem of an infinite loop caused by the
dependencies: it happen that it fails to start once every 2 launches
(features are loaded at bootstrap). I still believe that the
FeatureServiceImpl and the felix ResolverImpl have some kind of concurrency
problem, and managing the version of Hazelcast will only reduce the
probability of having a deadlock or livelock at startup, but it will not
fix it.







Il giorno mer 13 lug 2016 alle ore 12:13 Jamie G. <jamie.goodyear@gmail.com>
ha scritto:

> +1 (binding)
>
> Cheers,
> Jamie
>
> On Wed, Jul 13, 2016 at 4:25 AM, Cristiano Costantini
> <cristiano.costantini@gmail.com> wrote:
> > +1 (non binding)
> >
> >
> >
> > Il giorno mar 12 lug 2016 alle ore 18:36 Christian Schneider <
> > chris@die-schneider.net> ha scritto:
> >
> >> +1 (non binding)
> >>
> >> Christian
> >>
> >> 2016-07-11 22:27 GMT+02:00 Jean-Baptiste Onofré <jb@nanthrax.net>:
> >>
> >> > Hi all,
> >> >
> >> > I submit Apache Karaf Cellar 4.0.1 to your vote.
> >> >
> >> > Release Notes:
> >> >
> >> >
> >>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140&version=12334169
> >> >
> >> > Staging Repository:
> >> >
> https://repository.apache.org/content/repositories/orgapachekaraf-1067/
> >> >
> >> > Please vote to approve this release:
> >> >
> >> > [ ] +1 Approve the release
> >> > [ ] -1 Don't approve the release (please provide specific comments)
> >> >
> >> > This vote will be open for at least 72 hours.
> >> >
> >> > Thanks,
> >> > Regards
> >> > JB
> >> > --
> >> > Jean-Baptiste Onofré
> >> > jbonofre@apache.org
> >> > http://blog.nanthrax.net
> >> > Talend - http://www.talend.com
> >> >
> >>
> >>
> >>
> >> --
> >> --
> >> Christian Schneider
> >> http://www.liquid-reality.de
> >> <
> >>
> https://owa.talend.com/owa/redir.aspx?C=3aa4083e0c744ae1ba52bd062c5a7e46&URL=http%3a%2f%2fwww.liquid-reality.de
> >> >
> >>
> >> Open Source Architect
> >> http://www.talend.com
> >> <
> >>
> https://owa.talend.com/owa/redir.aspx?C=3aa4083e0c744ae1ba52bd062c5a7e46&URL=http%3a%2f%2fwww.talend.com
> >> >
> >>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message