You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2020/12/11 04:24:16 UTC
[Bug 64830] HTTP2 : GOAWAY sent with Protocol Error and Frame Size
Error
https://bz.apache.org/bugzilla/show_bug.cgi?id=64830
Arshiya <ar...@ericsson.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |---
--- Comment #18 from Arshiya <ar...@ericsson.com> ---
Hi Mark ,
I tried running the same test program with the latest tomcat 9.0.41 jars on
windows machine .
1.)I am still able to see the incomplete payload related exceptions and GOAWAY
(PROTOCOL_ERROR and FRAME_SIZE_ERROR) .
The test (payload size 55KB) ran for about 8 minutes where few requests had
timed-out (could see in JMeter GUI). On filtering the requests in the PCAP
captured with the unique identifier , I was able to find the trace for 3
requests with the below reason for GOAWAY (GOAWAY.pcap attached)
*) FRAME_SIZE_ERROR:The payload is [2128653] bytes long but the maximum frame
size is [16384]
*) PROTOCOL_ERROR :Connection [7004], Stream [1], The content length header
value [56,465] does not agree with the size of the data received [56,466]
*) PROTOCOL_ERROR :Connection [7092], Stream [1], The content length header
value [56,466] does not agree with the size of the data received [56,466]
Specs:
Windows 10
Processor:Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz 1.90GHz
RAM:16 GB
System Type : 64 bit
Please let me know in case of further inputs.
Thanks in advance!
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org