Hi guys,
I have been using Iago to replay HTTP logs and test against production-level systems. The distro I use has this commit at HEAD:
commit 41cf6a3ee5872c517ac14b948cfb85985a0cb558
Merge: 86c94d7 7f41856
Date: Tue Jan 13 13:30:39 2015 -0800
Merge pull request #42 from mzalimeni/master
Default maxRequests to Integer.MAX_VALUE rather than 1000
When I ramp up the request rate, I see many CLOSE_WAIT connections on my server, and the server becomes unresponsive. This happens even after I kill the Iago processes (via -k in the options, as recommended by the docs). The CLOSE_WAIT connections do not go away until after I reboot my service.
Our service uses Jetty under the covers, and I haven't found barely any issues with Jetty folks and CLOSE_WAIT.
Could it be that Iago is somehow not closing or cleaning up connections properly? Any ideas?
I'm planning to test the services using Apache bench or something else, but none of them quite test the system (using real logs) like Iago does.
thanks,
Evan