[
https://issues.apache.org/jira/browse/KARAF-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16832291#comment-16832291
]
Jean-Baptiste Onofré edited comment on KARAF-6271 at 5/6/19 2:56 PM:
---------------------------------------------------------------------
The karaf war example itest are working fine, at least with Java 8. So let me
try to reproduce however I'm surprised.
was (Author: jbonofre):
The karaf war example itest are working fine, at least with Java 8. So let me
try to reproduce buy I'm surprised.
> Issue with Pax web server and Jetty bundled in Karaf 4.2.5
> ----------------------------------------------------------
>
> Key: KARAF-6271
> URL: https://issues.apache.org/jira/browse/KARAF-6271
> Project: Karaf
> Issue Type: Bug
> Components: karaf
> Affects Versions: 4.2.5
> Reporter: Sebastiaan Hendriks
> Assignee: Jean-Baptiste Onofré
> Priority: Major
> Attachments: karaf.log
>
>
> First some context:
> I'm upgrading our application from Java 8 to Java 10+, moving from Karaf
> 3.0.8 to Karaf 4.2.x.
> The issue:
> In this application we got a War running for some maintenance screens for the
> end-user and I'm encountering an issue with the Pax web server unable to
> start since it is running up to a mismatch with the installed Jetty version,
> yielding the following error when our application feature is installed;
> 2019-05-02T14:25:39,732 | ERROR | paxweb-config-1-thread-1 | Activator
> | 135 - org.ops4j.pax.web.pax-web-runtime - 7.2.8 | Unable to
> start pax web server:
> org.eclipse.jetty.server.handler.HandlerCollection.<init>(Z)V
> java.lang.NoSuchMethodError:
> org.eclipse.jetty.server.handler.HandlerCollection.<init>(Z)V
> at
> org.ops4j.pax.web.service.jetty.internal.JettyServerHandlerCollection.<init>(JettyServerHandlerCollection.java:52)
> ~[?:?]
> at
> org.ops4j.pax.web.service.jetty.internal.JettyServerWrapper.<init>(JettyServerWrapper.java:146)
> ~[?:?]
> at
> org.ops4j.pax.web.service.jetty.internal.JettyServerImpl.<init>(JettyServerImpl.java:90)
> ~[?:?]
> at
> org.ops4j.pax.web.service.jetty.internal.JettyFactoryImpl.createServer(JettyFactoryImpl.java:99)
> ~[?:?]
> at
> org.ops4j.pax.web.service.jetty.internal.ServerControllerImpl$Stopped.start(ServerControllerImpl.java:380)
> ~[?:?]
> at
> org.ops4j.pax.web.service.jetty.internal.ServerControllerImpl.start(ServerControllerImpl.java:71)
> ~[?:?]
> at
> org.ops4j.pax.web.service.jetty.internal.ServerControllerImpl$Unconfigured.configure(ServerControllerImpl.java:700)
> ~[?:?]
> at
> org.ops4j.pax.web.service.jetty.internal.ServerControllerImpl.configure(ServerControllerImpl.java:87)
> ~[?:?]
> at
> org.ops4j.pax.web.service.internal.Activator.updateController(Activator.java:418)
> ~[?:?]
> at
> org.ops4j.pax.web.service.internal.Activator.lambda$scheduleUpdateFactory$1(Activator.java:344)
> ~[?:?]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:514) [?:?]
> at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1135)
> [?:?]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
> [?:?]
> at java.lang.Thread.run(Thread.java:844) [?:?]
>
> In an effort to narrow the source of the issue down, I've setup a simple
> feature where I am combining the karaf features Http, War and Webconsole to
> check if Karaf at its core can atleast run a webapplication. This yields the
> same error upon loading/starting the feature.
> Reproduction scenario:
> * Unpack a fresh install of Karaf 4.2.5
> * Setup a feature.xml in a repository somewhere containing the following;
> {color:#e8bf6a}<feature
> {color}{color:#bababa}name={color}{color:#6a8759}"spot-webconsole-attempt"
> {color}{color:#bababa}description={color}{color:#6a8759}"Feature to
> double-check web functionality"
> {color}{color:#bababa}install={color}{color:#6a8759}"auto"{color}{color:#e8bf6a}>
> {color}{color:#e8bf6a} <feature>{color}http{color:#e8bf6a}</feature>
> {color}{color:#e8bf6a} <feature>{color}war{color:#e8bf6a}</feature>
> {color}{color:#e8bf6a} <feature>{color}webconsole{color:#e8bf6a}</feature>
> {color}{color:#e8bf6a}</feature>{color}
> * Install on the shell with
> > feature:install -v {color:#6a8759}spot-webconsole-attempt{color}
> * Note error in karaf.log and console not reachable at
> [http://localhost:8181/system/console/bundles#|http://localhost:8181/system/console/bundles]
> org.apache.karaf.features.cfg relevant content;
> featuresRepositories = \
> mvn:org.apache.karaf.features/framework/4.2.5/xml/features, \
> mvn:org.apache.karaf.features/enterprise/4.2.5/xml/features, \
> mvn:org.apache.karaf.features/standard/4.2.5/xml/features, \
> mvn:org.apache.karaf.features/spring/4.2.5/xml/features, \
> mvn:org.apache.karaf.features/spring/4.0.1/xml/features, \
> mvn:nl.gvb.spot/spot-features/3.13-SNAPSHOT/xml/features, \
> mvn:nl.gvb.siri/siri-features/3.13-SNAPSHOT/xml/features, \
> mvn:nl.intraffic/spot-common-features/1.0.4-SNAPSHOT/xml/features
> featuresBoot = \
> instance/4.2.5, \
> package/4.2.5, \
> log/4.2.5, \
> ssh/4.2.5, \
> framework/4.2.5, \
> system/4.2.5, \
> eventadmin/4.2.5, \
> feature/4.2.5, \
> shell/4.2.5, \
> management/4.2.5, \
> service/4.2.5, \
> jaas/4.2.5, \
> deployer/4.2.5, \
> diagnostic/4.2.5, \
> wrap/2.6.1, \
> bundle/4.2.5, \
> config/4.2.5, \
> kar/4.2.5, \
> spring/3.2.0
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
