Or we can ask infra to create an account for this user :-)
2016-12-08 16:30 GMT+01:00 Jean-Baptiste Onofré <j...@nanthrax.net>: > Hi Dario, > > no worries, we will create the Jira for you. > > Thanks > Regards > JB > > On 12/08/2016 04:15 PM, Dario Amiri wrote: > >> Guillaume, >> >> Unfortunately, I don't have access to your JIRA. I've already provided a >> link with a project that can reproduce the issue, would you mind >> creating the issue for me? >> >> >> On 12/07/2016 08:13 AM, Guillaume Nodet wrote: >> >>> Could you please raise a JIRA with the above inforamtion ? >>> That looks like a bug... >>> >>> 2016-12-07 5:53 GMT+01:00 Dario Amiri <dariusham...@hotmail.com >>> <mailto:dariusham...@hotmail.com>>: >>> >>> >>> Here is a project on github that reproduces this issue: >>> https://github.com/damiri-ts/karaf-features-issue >>> <https://github.com/damiri-ts/karaf-features-issue> >>> >>> After more investigation, the root cause seems to be the inability >>> of karaf to gracefully handle situations where a child feature has >>> a prerequisite feature that is already installed as part of a >>> parent feature. It's confusing so I've included the feature >>> definition below. Note that the aries-blueprint feature shows up >>> twice. >>> >>> <feature name="something-else" version="${project.version}" >>> description="Something else"> >>> <feature prerequisite="true">jasypt-encryption</feature> >>> <feature prerequisite="true">aries-blueprint</feature> >>> </feature> >>> >>> <feature name="example" version="${project.version}" >>> description="Example"> >>> <feature>framework</feature> >>> <feature>wrap</feature> >>> <feature>aries-blueprint</feature> >>> <feature>shell</feature> >>> <feature>shell-compat</feature> >>> <feature>feature</feature> >>> <feature>jaas</feature> >>> <feature>ssh</feature> >>> <feature>management</feature> >>> <feature>bundle</feature> >>> <feature>config</feature> >>> <feature>deployer</feature> >>> <feature>diagnostic</feature> >>> <feature>instance</feature> >>> <feature>kar</feature> >>> <feature>log</feature> >>> <feature>package</feature> >>> <feature>service</feature> >>> <feature>system</feature> >>> >>> <feature>scr</feature> >>> <feature>jetty</feature> >>> <feature>pax-http-whiteboard</feature> >>> >>> <feature>something-else</feature> >>> </feature> >>> >>> On 12/06/2016 12:21 PM, Guillaume Nodet wrote: >>> >>>> You can use the --verbose flag when installing features. >>>> The actions performed should also be logged in the usual log file. >>>> >>>> 2016-12-06 20:05 GMT+01:00 Dario Amiri <dariusham...@hotmail.com >>>> <mailto:dariusham...@hotmail.com>>: >>>> >>>> Yes, I can reproduce it consistently. I believe all that is >>>> necessary to reproduce the issue is to install features >>>> aries-annotation/4.1.0-SNAPSHOT and pax-http/4.4.0 back to >>>> back. I am not doing anything more special than that. >>>> >>>> Is there additional logging I can turn on to get more insight >>>> into this issue? >>>> >>>> >>>> >>>> >>>> On Mon, Dec 5, 2016 at 11:41 PM -0800, "Guillaume Nodet" >>>> <gno...@apache.org <mailto:gno...@apache.org>> wrote: >>>> >>>> It's perfectly legal (and supported) to deploy a bundle in >>>> two different versions. >>>> In this case, I think the bundle has been uninstalled while >>>> waiting for the lock to start it, which could explain the >>>> exception you see. >>>> If the problem is reproductible, could you explain the steps ? >>>> >>>> 2016-12-06 3:49 GMT+01:00 Dario Amiri >>>> <dariusham...@hotmail.com <mailto:dariusham...@hotmail.com>>: >>>> >>>> I'm seeing errors like this when starting 4.1.0-SNAPSHOT >>>> >>>> 2016-12-05T18:23:57,843 | ERROR | FelixStartLevel | >>>> Felix | - - | Bundle >>>> org.objectweb.asm.all >>>> [54] Error locking mvn:org.ow2.asm/asm-all/6.0_ALPHA >>>> (java.lang.IllegalStateException: Bundle in unexpected >>>> state.) >>>> java.lang.IllegalStateException: Bundle in unexpected >>>> state. >>>> at >>>> org.apache.felix.framework.Fel >>>> ix.acquireBundleLock(Felix.java:5272) >>>> [?:?] >>>> at >>>> org.apache.felix.framework.Felix.setBundleStartLevel(Felix. >>>> java:1524) >>>> [?:?] >>>> at >>>> org.apache.felix.framework.Fra >>>> meworkStartLevelImpl.run(FrameworkStartLevelImpl.java:338) >>>> [?:?] >>>> at java.lang.Thread.run(Thread.java:745) [?:?] >>>> 2016-12-05T18:23:57,844 | INFO | CM Configuration Updater >>>> (ManagedService Update: pid=[org.apache.cxf.osgi]) | >>>> TldScanner | 189 - >>>> org.ops4j.pax.web.pax-web-jsp - >>>> 4.4.0 | found TLD bundle://189.0:0/META-INF/c.tl >>>> <http://c.tl>d >>>> 2016-12-05T18:23:57,841 | ERROR | FelixDispatchQueue | >>>> all | 184 - >>>> org.objectweb.asm.all - 5.0.2 | >>>> FrameworkEvent ERROR - org.objectweb.asm.all >>>> java.lang.IllegalStateException: Bundle in unexpected >>>> state. >>>> at >>>> org.apache.felix.framework.Fel >>>> ix.acquireBundleLock(Felix.java:5272) >>>> [?:?] >>>> at >>>> org.apache.felix.framework.Felix.setBundleStartLevel(Felix. >>>> java:1524) >>>> [?:?] >>>> at >>>> org.apache.felix.framework.Fra >>>> meworkStartLevelImpl.run(FrameworkStartLevelImpl.java:338) >>>> [?:?] >>>> at java.lang.Thread.run(Thread.java:745) [?:?] >>>> >>>> Digging around a bit I can see that there are conflicting >>>> versions of >>>> org.ow2.asm/asm-all between the aries-blueprint feature >>>> version >>>> 4.1.0-SNAPSHOT, which brings in aries-proxy which requires >>>> org.ow2.asm/asm-all/6.0_ALPHA, and pax-http feature >>>> version 4.4.0, which >>>> brings in pax-http-jetty which requires >>>> org.ow2.asm/asm-all/5.0.2. <http://5.0.2.> I'm >>>> not sure if this is what is causing the error in the logs. >>>> >>>> One other thing worth noting is that my bundle list only >>>> shows >>>> org.ow2.asm/asm-all/5.0.2 loaded but >>>> org.ow2.asm/asm-all/6.0_ALPHA is in >>>> the system directory of the container and I am perfectly >>>> able to load it >>>> manually after the container loads. I would welcome any >>>> input on how to >>>> resolve this issue. >>>> >>>> >>>> >>>> >>>> -- >>>> ------------------------ >>>> Guillaume Nodet >>>> ------------------------ >>>> Red Hat, Open Source Integration >>>> >>>> Email: gno...@redhat.com <mailto:gno...@redhat.com> >>>> Web: http://fusesource.com <http://fusesource.com/> >>>> Blog: http://gnodet.blogspot.com/ <http://gnodet.blogspot.com/> >>>> >>>> >>>> >>>> >>>> -- >>>> ------------------------ >>>> Guillaume Nodet >>>> ------------------------ >>>> Red Hat, Open Source Integration >>>> >>>> Email: gno...@redhat.com <mailto:gno...@redhat.com> >>>> Web: http://fusesource.com <http://fusesource.com/> >>>> Blog: http://gnodet.blogspot.com/ <http://gnodet.blogspot.com/> >>>> >>>> >>> >>> >>> >>> -- >>> ------------------------ >>> Guillaume Nodet >>> ------------------------ >>> Red Hat, Open Source Integration >>> >>> Email: gno...@redhat.com <mailto:gno...@redhat.com> >>> Web: http://fusesource.com <http://fusesource.com/> >>> Blog: http://gnodet.blogspot.com/ >>> >>> >> > -- > Jean-Baptiste Onofré > jbono...@apache.org > http://blog.nanthrax.net > Talend - http://www.talend.com > -- Apache Member Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead blog <http://notizblog.nierbeck.de/> Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS> Software Architect / Project Manager / Scrum Master
