We have noticed that WAPT does not close the TCP connections cleanly, but leaves the Apache server in FIN_WAIT_2 state. Is there a way to have WAPT send the final FIN-ACK? It should do so and leave the sockets in TIME_WAIT state, because it isn't we are concerned it may be skewing our results.
Thanks,
-Bob
Page 1 of 1
Apache TCP sessions not closed WAPT does not appear to be closing TCP session to the Apache server
#2
Posted 03 June 2009 - 11:10 AM
QUOTE (Bob R. @ Jun 1 2009, 09:49 PM) <{POST_SNAPBACK}>
We have noticed that WAPT does not close the TCP connections cleanly, but leaves the Apache server in FIN_WAIT_2 state. Is there a way to have WAPT send the final FIN-ACK? It should do so and leave the sockets in TIME_WAIT state, because it isn't we are concerned it may be skewing our results.
Thanks,
-Bob
Thanks,
-Bob
Please download the file wapt-50.zip here: http://www.loadtestingtool.com/forum/files/ and install the latest build of WAPT. Please let me know if the problem remains.
Angela Samsonova
Customer Support Manager
SoftLogica LLC.
Office: +7-383-335-6692
Toll-free: 1-888-364-6797 (for US only)
Time zone GMT +6, EST +11
E-mail: support@loadtestingtool.com
http://www.loadtestingtool.com
Customer Support Manager
SoftLogica LLC.
Office: +7-383-335-6692
Toll-free: 1-888-364-6797 (for US only)
Time zone GMT +6, EST +11
E-mail: support@loadtestingtool.com
http://www.loadtestingtool.com
Share this topic:
Page 1 of 1

Help











