https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/ODLPARENT-24 odlparent <p>Here is the exception that happens,</p> <p>MORAJA-M-301N:assembly moizr$ ./bin/karaf <br/> Error installing bundle listed in startup.properties with url: wrap:mvn:javax.servlet.jsp/jsp-api/2.1 and startlevel: 30<br/> Exception in thread "main" java.lang.NullPointerException<br/> at org.apache.karaf.main.Main.destroy(Main.java:525)<br/> at org.apache.karaf.main.Main.main(Main.java:173)</p> <p>To reproduce the problem,</p> <p>1. In the controller repo switch to the stable/lithium branch and build the controller using mvn clean install<br/> 2. cd ./karaf/opendaylight-karaf/target/assembly<br/> 3. ./bin/karaf</p> <p>The next time you try to launch karaf it will work. To reproduce again at this point do the following,</p> <p>1. stop/kill karaf<br/> 2. delete the data directory<br/> 3. ./bin/karaf</p> <p>Operating System: Mac OS<br/> Platform: Macintosh</p> ODLPARENT-24

Exception thrown when running karaf for the very first time

Bug Resolved Done Michael Vorburger Moiz Raja Fri, 11 Sep 2015 00:44:40 +0000 Wed, 24 Jan 2018 14:27:02 +0000 Wed, 7 Jun 2017 08:05:17 +0000 General 0 3 <p>Slightly more detailed exception,</p> <p>Sep 10, 2015 5:40:19 PM org.apache.karaf.main.Main launch<br/> INFO: Installing and starting initial bundles<br/> Sep 10, 2015 5:40:19 PM org.apache.karaf.main.Main main<br/> SEVERE: Could not launch framework<br/> java.lang.RuntimeException: Error installing bundle listed in startup.properties with url: wrap:mvn:javax.servlet.jsp/jsp-api/2.1 and startlevel: 30<br/> at org.apache.karaf.main.Main.installAndStartBundles(Main.java:392)<br/> at org.apache.karaf.main.Main.launch(Main.java:245)<br/> at org.apache.karaf.main.Main.main(Main.java:167)<br/> Caused by: java.lang.RuntimeException: Could not resolve wrap:mvn:javax.servlet.jsp/jsp-api/2.1<br/> at org.apache.karaf.main.util.SimpleMavenResolver.resolve(SimpleMavenResolver.java:59)<br/> at org.apache.karaf.main.Main.installAndStartBundles(Main.java:384)<br/> ... 2 more</p> <p>This seems to only happen on the controller distribution</p> <p>Hi Moiz,</p> <p>I still see reports of this occurring in master; do you know if a root cause was ever found for this? Any additional information you can provide is greatly helpful!</p> <p>Thanks!<br/> Ryan</p> <p>I'm just hitting something similar, with the infrautils SampleIntegrationTest which worked last week suddenly failing (both locally as well as on Jenkins) with this in infrautils/itestutils/it/target/surefire-reports/org.opendaylight.infrautils.itestutils.it.SampleIntegrationTest-output.txt:</p> <p>Error installing bundle listed in startup.properties with url: mvn:org.osgi/org.osgi.service.event/1.3.1 and startlevel: 7<br/> Exception in thread "main" java.lang.NullPointerException<br/> at org.apache.karaf.main.Main.destroy(Main.java:634)<br/> at org.apache.karaf.main.Main.main(Main.java:183)<br/> <span class="error">&#91;main&#93;</span> INFO org.ops4j.pax.exam.spi.reactors.ReactorManager - suite finished</p> <p>and indeed under infrautils/itestutils/it/target/paxexam/.../system/org there is no osgi/ sub-directory - should there be?</p> <p>Did we just break this by Or did we just break this when merging <a href="https://git.opendaylight.org/gerrit/#/c/58053/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/58053/</a> ?</p> <p>see also <a href="https://issues.apache.org/jira/browse/KARAF-3374" class="external-link" target="_blank" rel="nofollow noopener">https://issues.apache.org/jira/browse/KARAF-3374</a> for the Karaf issue which may in the future provide a better error message than the slightly confusing NullPointerException (but which won't fix the root cause which seems to be in our assembly).</p> <p>&gt; under system/org there is no osgi/ sub-directory - should there be?</p> <p>The real question is what needs org.osgi.service.event, and why that does not transitively pull it along... We can see controller.blueprint/pom.xml having a &lt;dependency&gt; to it, so is it missing in a controller feature?</p> <p>But as just raised in <a href="https://lists.opendaylight.org/pipermail/odlparent-dev/2017-June/001051.html" class="external-link" target="_blank" rel="nofollow noopener">https://lists.opendaylight.org/pipermail/odlparent-dev/2017-June/001051.html</a>, this currently happens even in odlparent and infrautils without controller in the picture:</p> <p>odlparent/karaf/opendaylight-karaf4-empty/target/assembly/bin/karaf<br/> Apache Karaf starting up. Press Enter to open the shell now...<br/> Error installing bundle listed in startup.properties with url:<br/> mvn:org.osgi/org.osgi.service.event/1.3.1 and startlevel: 7<br/> Exception in thread "main" java.lang.NullPointerException<br/> at org.apache.karaf.main.Main.destroy(Main.java:634)<br/> at org.apache.karaf.main.Main.main(Main.java:183)</p> <p><a href="https://git.opendaylight.org/gerrit/#/c/58362/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/58362/</a> fixes this (above), but I'm not 100% it's the right (or the best) fix .. I'm not clear what actually needs org.osgi.service.event in an empty basic Karaf, and why the Karaf core features that we depend on do not transitively pull this along - something seems off, that we have to do the kind of small work-around I'm proposing in c/58362.</p> <p>The fix should work. Controller's blueprint extension cannot just pull it in, as pax-logging has an optional dependency on it &#8211; leading to a complete container refresh when it pulled in.</p> <p>On the console this manifests by karaf printing the banner the second time.</p> <p>&gt; The fix should work.</p> <p>Confirming; FYI, I've now locally verified that merging c/58362 would fix both odlparent/karaf/opendaylight-karaf4-empty/target/assembly/bin/karaf as well as e.g. infrautils/itestutils/it (SampleIntegrationTest).</p> <p>&gt; pax-logging has an optional dependency on it</p> <p>Oh; didn't know. So... shouldn't it (org.osgi.service.event) then have been listed in some upstream Karaf core feature, in an ideal world, so that we would never have had this problem? (Open a bug / propose a change to Apache Karaf - or forget about it?)</p> <p>Closing as RESOLVED FIXED, as c/58362 got merged.</p> Development External issue ID 4290 External issue URL Issue Type ODL SR Target Milestone Rank 0|i022u7: