Greg Wilkins
Greg Wilkins
@sbordet @lorban @lachlan-roberts Do we think this is a problem? I lean to yes, as these listeners are part of our Debugging handler and have worked before. There are probably...
I've put in a work around for the DebugListener, so it now catches this exception and handles it correctly. Still not a perfect fix as there is still the cost...
@lorban The simple solution is to move the attributes map from the channel to the request. This would mean that after recycling a request could still be accessed, but the...
@lorban not a null map, a null value from the attribute get. Would be same behaviour as jetty-9,10,11. Still not entirely correct behavior.... but the same. Ultimately we need to...
> The QoSHandlerTest failures here are already fixed in HEAD. Actually I just disabled the tests for now....
@kelunik we've missed the deadline for the current release cycle. Moving this to next months release. If you can update the names, then I'm inclined to merge it in that...
@olamy please kill or resuscitate this PR
Can you give a full stack trace on the exception "org.eclipse.jetty.ee10.webapp.WebAppContext$Servlet ApiContext is not org.eclipse.jetty.server.handler.ContextHandler$ScopedContext" Also, before and after you start the server can you do a `server.dumpStdErr()`, and post...
@mperktold neither example really reproduces the issue that causes your production error. But it is indeed likely to be something related to the client acting badly and closing the connection...