You should verify that you haven’t saturated the network path to host -
otherwise as you say you are working around it - but all you’ve done is
effectively increase the timeout.
If you timestamp the messages and inspect on the receiver you may see that they
are significantly delayed.
> On Ma
Hi All,
I have been able to get around my issue by creating more than 1 connection
with the web server/service. I got this clue from a message I posted on
github issues page. Here is a link to the issue in case anyone is
interested:
https://github.com/golang/go/issues/52845
It appears that the HTT
Hi Robert, do you have any inputs about this ?
On Wednesday, 11 May 2022 at 08:31:24 UTC+10 envee wrote:
> Ok, so you can ignore my comment about the incomplete payload being sent.
> It is just that it is being sent in 2 frames as "partial entities".
> But I am still wondering why there is a con
Ok, so you can ignore my comment about the incomplete payload being sent.
It is just that it is being sent in 2 frames as "partial entities".
But I am still wondering why there is a context deadline exceeded which
then results in a RST_STREAM with CANCEL being sent by my client ?
it's just 100ms
Thanks for your reply, Robert.
I enabled GODEBUG for http2 in my client application and noticed the
following sequence of log lines for any particular stream for which I see
my client sending an RST_STREAM frame.
2022/05/10 21:59:12.827474 http2: Framer 0xc23f448000: wrote HEADERS
flags=END_HE
Conn.Error() should give you the underlying error as well.
> On May 10, 2022, at 7:47 AM, robert engels wrote:
>
> I would add some logging to
>
> func (cs *clientStream) cleanupWriteRequest(err error)
>
> but you should be getting the underlying error when you perform the next
> write on the
I would add some logging to
func (cs *clientStream) cleanupWriteRequest(err error)
but you should be getting the underlying error when you perform the next write
on the stream - maybe you are not processing this error properly (there is a
code - CANCEL, but also an err).
> On May 10, 2022, at
Set a breakpoint on the RST_STREAM generation and run under the debugger.
> On May 10, 2022, at 4:18 AM, envee wrote:
>
> Hi All, I am using a Go HTTP/2 client (no SSL) to send requests at the rate
> of around 3000 transactions per second (TPS) to a Web-server which is based
> on Netty.
>
>
Hi All, I am using a Go HTTP/2 client (no SSL) to send requests at the rate
of around 3000 transactions per second (TPS) to a Web-server which is based
on Netty.
At lower rates of say around 500 TPS , I do not see this issue, but at
rates as high as 2500 - 3000 TPS, I can see that my Go HTTP/2
