Support for Jetty 9.4 (and 9.3.15+) [SPR-14940]

[spring-projects-issues]

Juergen Hoeller opened SPR-14940 and commented

While Jetty 9.4 RC1 worked fine, RC2 seems to have broken HEAD handling (closing the HTTP connection too early for HEAD requests) which makes our AsyncRestTemplateIntegrationTests fail.

More importantly, Jetty 9.4 RC3 breaks our JettyRequestUpgradeStrategy now which turns this ticket into more than just a compatibility target. The underlying WebSocketServerFactory configuration changes seem to have been backported to Jetty 9.3.15 (even if not released yet), so we have to immediately backport them to Spring Framework 4.3.5 as well. That aside, we want Spring Framework 4.3.x to be compatible with Jetty 9.4 going forward in any case.

Due to those WebSocketServerFactory changes, we are technically unable to support WebSockets on Jetty 9.0.x any longer (but that branch got phased out in 2013 already). The support range is Jetty 9.1+ for Spring Framework 4.3.5+ now, and remains at Jetty 9.3+ for Spring Framework 5.0.

---

Issue Links:

• Release of 4.3.x supporting Jetty 9.4.0.v20161208+ [SPR-15027] #19594 Release of 4.3.x supporting Jetty 9.4.0.v20161208+ ("is duplicated by")
• RestTemplate POST and PUT don't work with Netty4ClientHttpRequestFactory [SPR-14860] #19426 RestTemplate POST and PUT don't work with Netty4ClientHttpRequestFactory
• Compatibility with Undertow 1.4 [SPR-14328] #18900 Compatibility with Undertow 1.4
• Support for Jetty 9.3 [SPR-13140] #17731 Support for Jetty 9.3
• Revisit dependency baseline: Jetty 9.4+, OkHttp 3+ [SPR-15038] #19604 Revisit dependency baseline: Jetty 9.4+, OkHttp 3+

0 votes, 5 watchers

[spring-projects-issues]

Juergen Hoeller commented

Brian Clozel, since Jetty 9.4 RC3 is out now and still seems to have broken HEAD handling with AsyncRestTemplate, could you have a look at this one please and potentially create a bug report for the Jetty guys?

On a related note, we also have #19426 where POST and PUT don't work with Netty4ClientHttpRequestFactory.

[spring-projects-issues]

Brian Clozel commented

Juergen Hoeller
I'm in the process of updating master to RC3; no problem with our client tests since in the meantime I updated them to use mockwebserver (we're already using this for the reactive client). I'll try to reproduce the issue anyway and see report it if necessary.

RC3 introduced a compatibility issue with our websocket support, I'm working on it.

[spring-projects-issues]

Juergen Hoeller commented

Alright, let's see whether that HEAD issue shows up in other tests. It always reported "connection closed" before us being able to parse the HTTP response there, with AsyncRestTemplate at least.

As for the 4.3.x branch, indeed, let's leave that on the Jetty 9.3 line. I've only marked this issue for 4.3.5 for potential Jetty 9.4 compatiblity fixes which we should backport, if any. Otherwise it's just a statement that we tested runtime compatibility with Jetty 9.4 in general and are happy to support its use with Spring Framework 4.3.5+ as well.

[spring-projects-issues]

Juergen Hoeller commented

Ouch, so they broke WebSocketServerFactory's initialization signatures... again :-( We've had to adapt between Jetty 9.0 vs 9.3 there already when the init method started taking a ServletContext, and now it seems to be the constructor taking it instead.

So this is not just a compatibility ticket anymore but rather an actual support ticket like #17731 was for Jetty 9.3.

[spring-projects-issues]

Brian Clozel commented

This change has been backported on their 9.3 branch as well, so we should backport our adaptation on 4.3.x as well.
In the meantime, a new version has been released "9.3.14.v20161028" but does not contain those changes.

[spring-projects-issues]

Brian Clozel commented

Just committed some changes - I'll close the issue when Jetty 9.4 will hit maven central so we can get proper releases as dependencies.