When I try to run a somewhat longer benchmark with our Quick Start application, I get strange timeouts while running ab (or siege)
ab -n 100000 -c 4 http://localhost:8080/ This is ApacheBench, Version 2.3 <$Revision: 1826891 $> Copyright 1996 Adam Twiss, Zeus Technology Ltd Licensed to The Apache Software Foundation Benchmarking localhost (be patient) Completed 10000 requests apr_socket_recv: Operation timed out (60) Total of 16347 requests completed The ab runs always fail at the 16348th request (when you use concurrency > 1 it will vary around 16348) I've upgraded/downgraded Wicket (this is still the case with 7.0, 7.10, 8.0, 8.1 and 8.2). I've upgraded jetty to the latest 9.4 version (9.4.14.v20181114) to no avail. Running ab on a remote Tomcat server does end normally, so it doesn't appear to be ab related (also siege exhibits the same behavior on the local Jetty server). Can anyone confirm this odd behavior? Martijn
