On Tue, Oct 6, 2020 at 12:13 PM Rémy Maucherat <r...@apache.org> wrote:
> On Tue, Oct 6, 2020 at 8:31 AM Martin Grigorov <mgrigo...@apache.org> > wrote: > > > Hi, > > > > I face an issue with the NIO2 protocol. > > When I increase the request rate to more than 500 requests per second it > > starts failing with: > > > > 06-Oct-2020 09:18:19.964 FINE [https-jsse-nio2-8080-exec-6] > > org.apache.coyote.http2.Http2UpgradeHandler.init Connection [1], State > > [NEW] > > 06-Oct-2020 09:18:19.978 FINE [https-jsse-nio2-8080-exec-6] > > org.apache.coyote.http2.Http2AsyncParser$FrameCompletionHandler.failed > > Connection [1], Stream [0], Frame type [null], Error > > java.io.EOFException > > at > > org.apache.tomcat.util.net > > .SecureNio2Channel$2.completed(SecureNio2Channel.java:1005) > > > > Also, it is a real EOF as the error says, caused by the client > disconnecting for whatever reason (good or bad). > The client is exactly the same for Tomcat NIO/NIO2/APR, Golang, Node.js, Rust and Netty. It works for all but NIO2. > > Rémy >
