Conn.Error() should give you the underlying error as well. > On May 10, 2022, at 7:47 AM, robert engels <reng...@ix.netcom.com> 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 stream - maybe you are not processing this error properly (there > is a code - CANCEL, but also an err). > >> On May 10, 2022, at 6:59 AM, Robert Engels <reng...@ix.netcom.com >> <mailto:reng...@ix.netcom.com>> wrote: >> >> Set a breakpoint on the RST_STREAM generation and run under the debugger. >> >>> On May 10, 2022, at 4:18 AM, envee <neeraj.vaidy...@gmail.com >>> <mailto:neeraj.vaidy...@gmail.com>> 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. >>> >>> 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 client sends >>> RST_STREAM frame right after transmitting the JSON payload via the DATA >>> frame. The Error in the RST_STREAM is seen as CANCEL even though the >>> response from the server for the Request has not been received. Also, there >>> is no timeout that has occured which might cause this. >>> >>> This occurs for some requests and not all, maybe about 100 out of the 3000 >>> per second. >>> >>> If you observe the screenshot attached, the HEADER is transmitted in packet >>> 118847 in stream id 49765. The DATA frame is in packet 122113. >>> >>> Right after that, the client transmits RST_STREAM for stream id 49765 in >>> packet 122277. >>> >>> And then this results in an error on the response from the Server in packet >>> 122483 and 122485 which says "Request stream 49765 is not correct for >>> server connection" >>> >>> Any clues what could be causing this issue of the client sending RST_STREAM >>> before receiving the HTTP response from the server ? >>> >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "golang-nuts" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to golang-nuts+unsubscr...@googlegroups.com >>> <mailto:golang-nuts+unsubscr...@googlegroups.com>. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/golang-nuts/56766546-356f-4901-b3d1-827be5bb0947n%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/golang-nuts/56766546-356f-4901-b3d1-827be5bb0947n%40googlegroups.com?utm_medium=email&utm_source=footer>. >>> <Screenshot 2022-05-10 190439.png> >
-- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/656ED8B8-B261-4DD6-8E48-921F86E1EF79%40ix.netcom.com.
