Repeated Request with HTTP2 Stall for long time

[Bhavesh Mistry]

HI Chromium team,

I would appreciate it if you guys help with the following issue. Basically, when the HTT2 request counter gets close to 400 to 550, request stall for while and continue again it will stall for 900 to 1050. 

https://bugs.chromium.org/p/chromium/issues/detail?id=1225774

It is quite easily reproducible. I can provide set-up.  Please ping me as this issue needs to be resolved.

It is related to 

https://bugs.chromium.org/p/chromium/issues/detail?id=1074705

.

Thanks,

Bhavesh 

[Bhavesh Mistry]

Based on debugging, it seems that when HTTP2 session ping fails the stalling is happening. What does this error mean and how does it impact outgoing requests from chrome browsers?

t=476451 [st=302960] HTTP2_SESSION_SEND_DATA
--> fin = true
--> size = 59
--> stream_id = 1021
t=486451 [st=312960] HTTP2_SESSION_CLOSE
--> description = "Failed ping."
--> net_error = -352 (ERR_HTTP2_PING_FAILED)
t=486452 [st=312961] HTTP2_SESSION_POOL_REMOVE_SESSION

Any help or pointer is really appreciated.

[Ryan Hamilton]

The ping failure means that the server did not respond to the PING Chrome sent in a timely fashion and so chrome closed the connection. Seems like the next step would be to dig into what is happening server side that prevents it from replying to the PING. 

--
--
Chromium Discussion mailing list: chromium...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-discuss

[Bhavesh Mistry]

Hi All,

I found the RCA of this was PING FRAME on tomcat was trying to close parent stream (which was NULL).  But, I still feel that the Chromium browser must be more robust, IF SESSION liveliness fails, the chromium should tear down the existing connection, and open a new one.  Why is  request being stalled for ( 2 minutes to 11 minutes). 

Fix on Tomcat:  https://github.com/apache/tomcat/pull/431 

Any opinion on how to make the Chromium browser more resilient to this kind of error?

Thanks,

Bhavesh