Ludovic Orban

@konstantin-mikheev We're currently re-investigating this problem, and it seems there are at least a couple of issues at play; I managed to reproduce one of them and I'm working on...

@konstantin-mikheev I've created a PR containing a simple change that should mitigate this problem, it's over here: https://github.com/jetty/jetty.project/pull/11637 For some reason I'm still investigating, the HTTP2 headers can become corrupted...

The loop got sorted out but the original NPE still exists. I've opened https://github.com/jetty/jetty.project/issues/11785 to follow up on that one. Again, if you could come up with a reproducer that...

What I generally like: - The `writeTo()` pattern as the less we have to call `getByteBuffer()` the better. - The `append()` pattern for the same reason as above. - The...

Here is my theory about what could be the cause of this: **TL;DR** _I think Jersey is reading from the `ServletInputStream` while the core `Handler`'s callback is being succceeded._ IAE...

@perok Can you create a reproducer and publish it as some github repo? While the symptoms of your EE8 problem look similar to the original EE10 one, EE8/9 have a...

So you're basically suggesting to take both timestamps and checking them in the `HttpInput.read()` method? This sounds like the most straightforward and reasonable method to me.

So you mean you were calling `Callback.succeeded()` more than once? In that case, that's indeed your error and it could lead to such exception. Thanks for the explanation!

Here is the output when the test fails: ``` Running org.eclipse.jetty.ee8.websocket.tests.client.ClientCloseTest.testMessageTooLargeException() 2024-04-18 10:35:30.663:INFO :oejsh.ContextHandler:ForkJoinPool-1-worker-3: Started oeje8n.ContextHandler$CoreContextHandler@672da6a0{ROOT,/,b=null,a=AVAILABLE,h=oeje8n.ContextHandler$CoreContextHandler$CoreToNestedHandler@46397f32{STARTED}} 2024-04-18 10:35:30.663:INFO :oejs.DefaultSessionIdManager:ForkJoinPool-1-worker-3: Session workerName=node0 2024-04-18 10:35:30.664:INFO :oejs.AbstractConnector:ForkJoinPool-1-worker-3: Started ServerConnector@442b9b9b{HTTP/1.1, (http/1.1)}{0.0.0.0:38413} 2024-04-18 10:35:30.664:INFO :oejs.Server:ForkJoinPool-1-worker-3:...

Here is the captured output: ``` Running org.eclipse.jetty.client.HttpClientGZIPTest.testLargeGZIPContentDoesNotPolluteByteBufferPool([2] HTTPS) 2024-04-21 19:25:47.769:INFO :oejs.Server:ForkJoinPool-1-worker-4: jetty-12.0.9-SNAPSHOT; built: 2024-04-18T15:02:22.962Z; git: 4a943c9558f354c13c1f866e11c44d1836dede82; jvm 17.0.9+9 2024-04-21 19:25:47.830:INFO :oejs.Server:ForkJoinPool-1-worker-2: Stopped oejs.Server@5508355d{STOPPING}[12.0.9-SNAPSHOT,sto=0] 2024-04-21 19:25:47.830:INFO :oejus.SslContextFactory:ForkJoinPool-1-worker-4: x509=X509@3bb1b274(mykey,h=[localhost],a=[/127.0.0.1, /0:0:0:0:0:0:0:1],w=[]) for...