Jump to content


Apache TCP sessions not closed


  • Please log in to reply
1 reply to this topic

#1 Guest_Bob R._*

Guest_Bob R._*
  • Guests

Posted 01 June 2009 - 02:49 PM

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



#2 Guest_angela_*

Guest_angela_*
  • Guests

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


Please download the file wapt-50.zip here: http://www.loadtesti...om/forum/files/ and install the latest build of WAPT. Please let me know if the problem remains.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users