https://bz.apache.org/bugzilla/show_bug.cgi?id=65776
--- Comment #18 from Mark Thomas ---
*** Bug 66476 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are the assignee for the bug.
https://bz.apache.org/bugzilla/show_bug.cgi?id=65776
Mark Thomas changed:
What|Removed |Added
CC||patkarom...@gmail.com
--- Comment #17
https://bz.apache.org/bugzilla/show_bug.cgi?id=65776
Mark Thomas changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://bz.apache.org/bugzilla/show_bug.cgi?id=65776
--- Comment #15 from Mark Thomas ---
The large drop in throughput I reported in comment #7 has been bothering me so
I wanted to look at this again.
Testing this is tricky as you can quickly run out of ephemeral ports. Once that
happens, test
https://bz.apache.org/bugzilla/show_bug.cgi?id=65776
Mark Thomas changed:
What|Removed |Added
Status|NEEDINFO|NEW
--- Comment #14 from Mark Thomas
https://bz.apache.org/bugzilla/show_bug.cgi?id=65776
--- Comment #13 from Brooke T. Hedrick ---
@Mark
RE: https://bz.apache.org/bugzilla/show_bug.cgi?id=65776#c12
- Bare metal or VM? VM
- If VM, which hypervisor? VMWare ESX 7.x
- What sort of load (in terms of new connections per second) was
https://bz.apache.org/bugzilla/show_bug.cgi?id=65776
Mark Thomas changed:
What|Removed |Added
Status|NEW |NEEDINFO
--- Comment #12 from Mark
https://bz.apache.org/bugzilla/show_bug.cgi?id=65776
--- Comment #11 from Brooke T. Hedrick ---
Not sure if this is useful, but running the test with WSL and Ubuntu 20.04.3
LTS
2 "console windows" running the wrk at the same time.
This is how the server failed
Listening on port
https://bz.apache.org/bugzilla/show_bug.cgi?id=65776
Brooke T. Hedrick changed:
What|Removed |Added
CC||brooke.t.hedr...@gmail.com
--
https://bz.apache.org/bugzilla/show_bug.cgi?id=65776
--- Comment #10 from Brooke T. Hedrick ---
Hey Christopher Schultz,
RE>
Are you able to compile+run the C-language test driver which is mentioned
above? I'm not sure it will even compile on Windows but it would be interesting
to see what
https://bz.apache.org/bugzilla/show_bug.cgi?id=65776
--- Comment #9 from Christopher Schultz ---
(In reply to Brooke T. Hedrick from comment #8)
> We are seeing this error on Windows Server 2019
Uh oh. This is supposed to be a Linux kernel bug.
> Apache Tomcat 9.0.56
> We do NOT see this
https://bz.apache.org/bugzilla/show_bug.cgi?id=65776
--- Comment #8 from Brooke T. Hedrick ---
We are seeing this error on Windows Server 2019
Jan 21, 2022 10:30:21 AM org.apache.tomcat.util.net.AprEndpoint
setSocketOptions
SEVERE: Error allocating socket processor
java.io.IOException:
https://bz.apache.org/bugzilla/show_bug.cgi?id=65776
--- Comment #7 from Mark Thomas ---
Checking the time since the last accept adds a significant overhead. With a
simply JMeter test with keep-alive disabled, throughput dropped by 75% once I
added the timing check. That level of overhead isn't
https://bz.apache.org/bugzilla/show_bug.cgi?id=65776
--- Comment #6 from Mark Thomas ---
That should only be an issue if:
- there are no other connections to the server between liveness checks
- the liveness checks are >= time_wait seconds apart
Increasing the frequency of the liveness checks
https://bz.apache.org/bugzilla/show_bug.cgi?id=65776
Sunwoo changed:
What|Removed |Added
Status|NEEDINFO|NEW
--- Comment #5 from Sunwoo ---
I'm
https://bz.apache.org/bugzilla/show_bug.cgi?id=65776
--- Comment #4 from Mark Thomas ---
The simplest thing to do is to run the pure C test case provided in the Java
bug report:
https://bz.apache.org/bugzilla/show_bug.cgi?id=65776
Mark Thomas changed:
What|Removed |Added
Status|NEW |NEEDINFO
--- Comment #3 from Mark
https://bz.apache.org/bugzilla/show_bug.cgi?id=65776
--- Comment #2 from Johnny Lim ---
Thanks for the quick feedback!
I just assumed that it's a Ubuntu-specific bug as it's reported against the
Ubuntu issue tracker. I haven't had time looking into it closely yet, so it was
just one of possible
https://bz.apache.org/bugzilla/show_bug.cgi?id=65776
--- Comment #1 from Mark Thomas ---
This scenario was considered when designing the protection for the OS bug. The
solution considered was to add a timing check for the re-use as in the OS bug
case the re-use is near enough instant. However,
19 matches
Mail list logo
