https://bz.apache.org/bugzilla/show_bug.cgi?id=64621
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #8 from Mark Thomas <ma...@apache.org> ---
Without the ability to recreate this issue the only way to test if the issue is
resolved is going to be in production.
Based on the additional information provided, I expanded the test cases to
cover two scenarios:
a) ensuring after active stream limit is reached, new streams are allowed once
the number of current active streams falls
b) ensuring that client cancelled streams are removed from the active stream
count
test a) passed.
Test b) identified a bug where cancelled streams weren't removed from the
active stream count. I suspect this is at least part of, possibly all of, the
cause of the issues you are seeing.
The bug has been fixed in:
- master for 10.0.0-M8 onwards
- 9.0.x for 9.0.38 onwards
- 8.5.x for 8.5.58 onwards
Those releases are expected in early September. You are, of course, free to
build from source and test before then.
Absent any further information, I am going to assume that this issue is now
fixed.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
