Lachlan

@minduch now I don't think the ALPN default protocol is actually related to your issue. I can actually run your code without modifications and connect to WebSocket over HTTP/2. Here...

@horiavmuntean can you try running this project ([websocket-http2-embedded-example](https://github.com/lachlan-roberts/websocket-http2-embedded-example)) and tell me if that works for you. I have not tried on your JDK but this does work fine for me...

Jetty 9.4 has reached the end of community support (see https://github.com/eclipse/jetty.project/issues/7958). If you upgrade to Jetty 10 do you still encounter this error? Jetty 10 has major changes to the...

@pshevche the problem does not currently exist in Jetty 10 as the failure is ignored with a NOOP callback, the PR #8356 is really just a cleanup to make things...

@joakime Can you look at the disabled test `org.eclipse.jetty.ee10.servlet.DefaultServletTest#testListingFilenamesOnlyUrlResource` in relation to the changes in this PR. Is using `jar:file` URIs and in `12.0.x` was failing because it was being...

@joakime no this does not need to be in the `10.0.10` release. I think it also needs some performance testing to assess the impact of this.

@ssk512 Can you give more context to when you are getting this error. Is this just from running this example project with no changes? This would happen if the client...

@joakime do you know if this can be closed after the #6581 PR?

Looks like the windows run on jetty-10.0.x seems to be passing on jenkins. https://jenkins.webtide.net/job/nightlies/job/jetty-10.0.x-windows-nightly/ Although there is some failures for jdk-17 https://jenkins.webtide.net/job/nightlies/job/jetty-10.0.x-windows-nightly-jdk17/

@joakime no, the benchmarks indicated that using the wrapper around methodhandle is significantly slower. So we need to further assess the performance impact this change would have. I don't think...