Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

wiremock is not working with jetty 9.4.29.v20200521

See original GitHub issue

I’m using com.github.tomakehurst:wiremock-jre8:2.26.3

and the commit that I believe is the culprit https://github.com/eclipse/jetty.project/commit/46ad90598c65d127124395db32172f381579a825#r39400262

java.lang.NoSuchMethodError: 'java.nio.channels.ByteChannel org.eclipse.jetty.io.ChannelEndPoint.getChannel()'
	at com.github.tomakehurst.wiremock.jetty9.JettyFaultInjector.socket(JettyFaultInjector.java:92)
	at com.github.tomakehurst.wiremock.jetty9.JettyFaultInjector.<init>(JettyFaultInjector.java:44)
	at com.github.tomakehurst.wiremock.jetty9.JettyFaultInjectorFactory.buildFaultInjector(JettyFaultInjectorFactory.java:49)
	at com.github.tomakehurst.wiremock.servlet.WireMockHandlerDispatchingServlet.buildFaultInjector(WireMockHandlerDispatchingServlet.java:228)
	at com.github.tomakehurst.wiremock.servlet.WireMockHandlerDispatchingServlet.applyResponse(WireMockHandlerDispatchingServlet.java:198)
	at com.github.tomakehurst.wiremock.servlet.WireMockHandlerDispatchingServlet$ServletHttpResponder.respondTo(WireMockHandlerDispatchingServlet.java:183)
	at com.github.tomakehurst.wiremock.servlet.WireMockHandlerDispatchingServlet$ServletHttpResponder.respondSync(WireMockHandlerDispatchingServlet.java:150)
	at com.github.tomakehurst.wiremock.servlet.WireMockHandlerDispatchingServlet$ServletHttpResponder.respond(WireMockHandlerDispatchingServlet.java:144)
	at com.github.tomakehurst.wiremock.http.AbstractRequestHandler.handle(AbstractRequestHandler.java:90)
	at com.github.tomakehurst.wiremock.servlet.WireMockHandlerDispatchingServlet.service(WireMockHandlerDispatchingServlet.java:120)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:590)

Issue Analytics

State:
Created 3 years ago
Comments:5

Top GitHub Comments

3reactions

fatih-erdemcommented, Jun 16, 2020

I’ve upgraded one of our projects to Spring Boot 2.3.1 and a couple of tests got broke. Because with this version of Spring Boot, they have upgraded Jetty to 9.4.29.v20200521.

2reactions

tomakehurstcommented, May 24, 2020

There will be a Jetty upgrade in the next release.

In the meantime try the standalone version, as this shades Jetty.

Top Results From Across the Web

[jetty-users] Jetty fails to start because of a problem in jetty.xml

It worked until we decided to upgrade the jetty version from 8.1.10.v20130312 to 9.4.29.v20200521. Now the server fails to start. I'm trying to ......

EvoMaster/pom.xml at master · EMResearch ... - GitHub

Used to calculate code-coverage of the tests. Note: Kotlin still has problems, as its compiler not marking. yet the automatically generated/added functions.

Cloud Native Core Licensing Information User Manual

Provider Component (s) Licensing Information Apache 2.0 akka‑cluster‑sharding 2.5.22 APACHE 2.0 ‑See Appendix E Apache 2.0 akka‑cluster‑sharding 2.6.5 APACHE 2.0 ‑See Appendix E Apache 2.0 akka‑cluster‑sharding...

Jetty :: ALPN :: Conscrypt Server Implementation - javalibs

Jetty :: ALPN :: Conscrypt Server Implementation. homepage: fresh index: new artifact: ... 9.4.29.v20200521 (21.5.2020) release central ...

org.eclipse.jetty » jetty-util - Maven Repository

Jetty Core :: Utilities. Utility classes for Jetty. License, Apache 2.0EPL 2.0. Tags, servereclipsewebserver ... Jun 12, 2020. 9.4.29.v20200521 · Central.