On 25/09/2020 15:47, Arshiya Shariff wrote:
> Thanks for the response Martin.
>
> Below is the only exception we are getting in the logs while sending response
> to a closed stream , few times with MUST_COMPLETE instead of MUST_ERROR :
> Exception occurred while sending response.
Thanks for the response Martin.
Below is the only exception we are getting in the logs while sending response
to a closed stream , few times with MUST_COMPLETE instead of MUST_ERROR :
Exception occurred while sending response. ExceptionMessage:Calling
[asyncComplete()] is not valid for a
On Fri, Sep 25, 2020 at 1:18 PM Arshiya Shariff
wrote:
> Thanks Martin .
>
> Our expectation Is that , on receiving a RST_STREAM with CANCEL or
> NO_ERROR from the client after 1.5 secs for a particular stream , we don’t
> want the connection to be closed with a GOAWAY:NO_ERROR (while trying
Thanks Martin .
Our expectation Is that , on receiving a RST_STREAM with CANCEL or NO_ERROR
from the client after 1.5 secs for a particular stream , we don’t want the
connection to be closed with a GOAWAY:NO_ERROR (while trying to send response
after 2secs asynchronously over a stream that
Hi,
On Tue, Sep 22, 2020 at 1:47 PM Arshiya Shariff
wrote:
> Thank you so much Martin for the response.
> Yes , 9.0.38 testing is on going .
>
> As we don’t get this clear with the RFC , please help us with the below
> two cases :
* If a client sends RST_STREAM with NO_ERROR, then while
Thank you so much Martin for the response.
Yes , 9.0.38 testing is on going .
As we don’t get this clear with the RFC , please help us with the below two
cases :
* If a client sends RST_STREAM with NO_ERROR, then while sending async
response is it expected behavior to close connection with
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
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