Re: Low throughput with HTTP2

On 21/09/2020 15:52, Mark Thomas wrote: > That doesn't > exclude, of course, the possibility of improving how Tomcat handles > traffic like this. Looks like Tomcat could prune the closed streams less aggressively. At the moment it waits until there are maxConcurrentStreams + 10% in the map

ANN: Bill Stewart's Apache Tomcat Setup for Windows [9.0.38]

Documentation and installer source: https://github.com/Bill-Stewart/ApacheTomcatSetup Download installer: https://github.com/Bill-Stewart/ApacheTomcatSetup/releases - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org

Re: Low throughput with HTTP2

On Mon, Sep 21, 2020 at 9:31 PM Martin Grigorov wrote: > > > On Mon, Sep 21, 2020 at 5:52 PM Mark Thomas wrote: > >> On 21/09/2020 13:48, Martin Grigorov wrote: >> > Hi Remy, >> > >> > On Mon, Sep 21, 2020 at 2:56 PM Rémy Maucherat wrote: >> > >> > >> > >> > >> >>> 2020-09-21 14:25:04.850

Re: Low throughput with HTTP2

On Mon, Sep 21, 2020 at 5:52 PM Mark Thomas wrote: > On 21/09/2020 13:48, Martin Grigorov wrote: > > Hi Remy, > > > > On Mon, Sep 21, 2020 at 2:56 PM Rémy Maucherat wrote: > > > > > > > > > >>> 2020-09-21 14:25:04.850 DEBUG 232086 --- [https-jsse-nio-18080-exec-8] > >>>

Re: Low throughput with HTTP2

On 21/09/2020 13:48, Martin Grigorov wrote: > Hi Remy, > > On Mon, Sep 21, 2020 at 2:56 PM Rémy Maucherat wrote: > > > > >>> 2020-09-21 14:25:04.850 DEBUG 232086 --- [https-jsse-nio-18080-exec-8] >>> o.a.coyote.http11.Http11NioProtocol : Found processor [null] for >>> socket

HTTP2: Tomcat sends GOAWAY when trying to respond over a stream where the client has already sent RST_STREAM:NO ERROR

Hi All, The client has configured a response timeout of 1.5 seconds. In a case when our application tries to respond over a http2 stream asynchronously after 2 seconds where the client has already sent RST_STREAM with NO ERROR in 1.5 seconds (due to no response) , then tomcat sends GOAWAY and

Re: HTTP2: Tomcat sends GOAWAY when trying to respond over a stream where the client has already sent RST_STREAM:NO ERROR

Hi, On Mon, Sep 21, 2020 at 7:56 PM Arshiya Shariff wrote: > Hi All, > > The client has configured a response timeout of 1.5 seconds. In a case > when our application tries to respond over a http2 stream asynchronously > after 2 seconds where the client has already sent RST_STREAM with NO ERROR

Adding regular expression support to CORS filter

Hi there, I'd like to contribute a CORS filter enhancement, making it accept both wildcard-based and 'regular expression'-based expressions for its allowed origins list. I know this from a project based on Jetty, which has support for, at least, simple wildcard matching (*). Specifying

Re: Low throughput with HTTP2

On Mon, Sep 21, 2020 at 11:23 AM Mark Thomas wrote: > On 21/09/2020 08:18, Martin Grigorov wrote: > > On Fri, Sep 18, 2020 at 6:16 PM Mark Thomas wrote: > > > >> On 18/09/2020 14:07, Martin Grigorov wrote: > >> > >> > >> > >>> What is the difference > >>> between

Re: Low throughput with HTTP2

On Mon, Sep 21, 2020 at 12:08 PM Martin Grigorov wrote: > > > On Mon, Sep 21, 2020 at 11:23 AM Mark Thomas wrote: > >> On 21/09/2020 08:18, Martin Grigorov wrote: >> > On Fri, Sep 18, 2020 at 6:16 PM Mark Thomas wrote: >> > >> >> On 18/09/2020 14:07, Martin Grigorov wrote: >> >> >> >> >> >>

Re: Low throughput with HTTP2

On 21/09/2020 08:18, Martin Grigorov wrote: > On Fri, Sep 18, 2020 at 6:16 PM Mark Thomas wrote: > >> On 18/09/2020 14:07, Martin Grigorov wrote: >> >> >> >>> What is the difference >>> between org.apache.coyote.http2.StreamStateMachine.State#CLOSED_RX >>> and

Re: Low throughput with HTTP2

On Fri, Sep 18, 2020 at 6:16 PM Mark Thomas wrote: > On 18/09/2020 14:07, Martin Grigorov wrote: > > > > > What is the difference > > between org.apache.coyote.http2.StreamStateMachine.State#CLOSED_RX > > and org.apache.coyote.http2.StreamStateMachine.State#CLOSED_TX ? > > Compare the

Re: Low throughput with HTTP2

On 21/09/2020 10:44, Martin Grigorov wrote: > On Mon, Sep 21, 2020 at 12:08 PM Martin Grigorov > wrote: >> On Mon, Sep 21, 2020 at 11:23 AM Mark Thomas wrote: >>> RFC 7540 allows the connection to be closed with a protocol error if the >>> reset is received "a significant time after sending

Re: Low throughput with HTTP2

On Mon, Sep 21, 2020 at 2:49 PM Martin Grigorov wrote: > Hi Remy, > > On Mon, Sep 21, 2020 at 2:56 PM Rémy Maucherat wrote: > > > > > > > 2020-09-21 14:25:04.850 DEBUG 232086 --- [https-jsse-nio-18080-exec-8] > > > o.a.coyote.http11.Http11NioProtocol : Found processor [null] for > > >

Re: Low throughput with HTTP2

On Mon, Sep 21, 2020 at 12:08 PM Martin Grigorov wrote: > > > On Mon, Sep 21, 2020 at 11:23 AM Mark Thomas wrote: > >> On 21/09/2020 08:18, Martin Grigorov wrote: >> > On Fri, Sep 18, 2020 at 6:16 PM Mark Thomas wrote: >> > >> >> On 18/09/2020 14:07, Martin Grigorov wrote: >> >> >> >> >> >>

Re: Low throughput with HTTP2

On Mon, Sep 21, 2020 at 3:48 PM Martin Grigorov wrote: > Hi Remy, > > On Mon, Sep 21, 2020 at 2:56 PM Rémy Maucherat wrote: > > > > >> > 2020-09-21 14:25:04.850 DEBUG 232086 --- [https-jsse-nio-18080-exec-8] >> > o.a.coyote.http11.Http11NioProtocol : Found processor [null] for >> > socket

Re: Low throughput with HTTP2

On Mon, Sep 21, 2020 at 1:36 PM Martin Grigorov wrote: > On Mon, Sep 21, 2020 at 12:08 PM Martin Grigorov > wrote: > > > > > > > On Mon, Sep 21, 2020 at 11:23 AM Mark Thomas wrote: > > > >> On 21/09/2020 08:18, Martin Grigorov wrote: > >> > On Fri, Sep 18, 2020 at 6:16 PM Mark Thomas wrote: >

Re: Low throughput with HTTP2

Hi Remy, On Mon, Sep 21, 2020 at 2:56 PM Rémy Maucherat wrote: > > 2020-09-21 14:25:04.850 DEBUG 232086 --- [https-jsse-nio-18080-exec-8] > > o.a.coyote.http11.Http11NioProtocol : Found processor [null] for > > socket [org.apache.tomcat.util.net.SecureNioChannel@2b435926 > >