[Bug 65773] New: WINDOW_UPDATE NOT SENT

2021-12-30 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=65773 Bug ID: 65773 Summary: WINDOW_UPDATE NOT SENT Product: Tomcat 9 Version: 9.0.38 Hardware: PC OS: Linux Status: NEW Severity: blocker Priority:

[Bug 65773] WINDOW_UPDATE NOT SENT

2021-12-30 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=65773 --- Comment #1 from Michael Osipov --- Upgrade first. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomc

[Bug 65773] WINDOW_UPDATE NOT SENT

2021-12-30 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=65773 --- Comment #2 from Arshiya --- The application was working fine with the same version since few months , so we want to find the RCA as to why the issue has occurred . Was there any fix around this that went in post 9.0.38 so we can update the

[Bug 65773] WINDOW_UPDATE NOT SENT

2021-12-30 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=65773 --- Comment #3 from EJ Egyed --- There are several fixes to HTTP/2 window updates between version 9.0.38 and 9.0.56 (current latest). You can review the changes here https://tomcat.apache.org/tomcat-9.0-doc/changelog.html and just do a quick se

[Bug 65773] WINDOW_UPDATE NOT SENT

2021-12-30 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=65773 Christopher Schultz changed: What|Removed |Added Status|NEW |NEEDINFO --- Comment #4 from Chr

[Bug 65775] New: fgets_unlocked crash on CentOS 7 (and Ubuntu 14.04) in Tomcat 9.0.12 through 9.0.54 (and others)

2021-12-30 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=65775 Bug ID: 65775 Summary: fgets_unlocked crash on CentOS 7 (and Ubuntu 14.04) in Tomcat 9.0.12 through 9.0.54 (and others) Product: Tomcat 9 Version: 9.0.x Hardware: PC

[Bug 65773] WINDOW_UPDATE NOT SENT

2021-12-30 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=65773 --- Comment #5 from Arshiya --- As tomcat abruptly stops sending the WINDOW_UPDATE we are unable to reproduce the issue in the test environment and find where the issue is . Can we have any scenarios to simulate a case where tomcat suddenly st