Time_wait too many workarounds for Linux and Windows

Http://www.51testing.com/html/48/202848-249774.html

Time_wait too many workarounds for Linux and Windows

http://m.sohu.com/a/122714498_412810

Windows time_wait Too many workarounds

Bath Dawn:
is a problem with the configuration:
Besides the need to configure MaxUserPort in addition to Tcpwaitdelay, the range of dynamic ports also needs to be added. netsh int ipv4 set dynamicport tcp start=1025 num=60000
Bath Dawn:
The value of Tcpwaitdelay must be Microsoft's official recommended value (DWORD value is 1e)
I tried to change it to 1 or 5.
Bath Dawn:
Instead of the 30 problem disappears guess if the value is not 30 to 300 use the default value of 240
Bath Dawn:
Which means four minutes to recycle the TCP link.

Baidu came to the answer to what 1 or 0 ...
It's not right.

Apache multiple requests with Jmeterask Question

Up vote0down votefavorite1

I am using Jmeter to test multiple requests to my Web application. I used in NumberOfThread Jmeter as 50. My process is as follows: Login page. Login with UserID and password. Show Menu page. Click Search page. Go to search page. Click the Search button. Click The searched result link to go to update page. Update data and click Update button. Show the updated result page. Go back to search page. Log out button click. In the above process, I used looping controller for process number 5 to ten with 5 looping. In this situation, if I used more than, the thread to run Jmeter test, have address already in use, the socket binding exception occur. I would like to know how to solve that problem. Java Apache JMeter jboss5.x ShareImprove this question Edited Jan 8 ' at 11:46aliaksandr Belik9,2105 Asked Jan 7 ' at 11:15pyisoemaw16

Add a Comment

1 answeractiveoldestvotes

Up vote7down voteaccepted

Looks like your client ran out of ephemeral port or there ' s some problem with your client environment. Is you using Windows? You can possibly does at least the following: Windows:look into this article for solution for Windows system as host for JMeter. Use the Linux system instead as host to run Jmeter Load-scenarios. As well you possibly'll find this article useful for your testing activities (I ' ve seen Jboss in tags). UPDATE: Once more from linked article above: When an HTTP request was made, an ephemeral port was allocated for the TCP/IP connection. The ephemeral port range is 32678–61000. After the client closes the connection, the connection are placed in the time-wait state for the seconds. If JMeter (HttpClient) is sending thousands of HTTP requests per second and creating new TCP/IP connections, the system Would run out of available ephemeral ports for allocation. . . . Otherwise, the following messages may appear in the JMeter JTL files: Non HTTP Response Code:java.net.BindException Non HTTP response message:address already in use The solution is to enable fast recycling time_wait sockets. Echo 1 >/proc/sys/net/ipv4/tcp_tw_recycle Other options include tcp_fin_timeout to reduce how long a connection are placed in the TIME_WAIT state and Tcp_tw_reuse to Allow the system to reuse connections placed in the TIME_WAIT state. On the server ' s side: This enables fast recycling of time_wait sockets /sbin/sysctl -w net.ipv4.tcp_tw_recycle=1 This allows reusing sockets in time_wait state for new connections-a safer alternative to Tcp_tw_recycle /sbin/sysctl -w net.ipv4.tcp_tw_reuse=1 The Tcp_tw_reuse setting is particularly useful in environments where numerous short connections be open and left in time _wait state, such as Web-servers. Reusing the sockets can is very effective in reducing server load. Maximum number of TIMEWAIT sockets held by system simultaneously /sbin/sysctl -w net.ipv4.tcp_max_tw_buckets=30000 or the same but in another way-add the lines below to the file so, the change /etc/sysctl.conf survives reboot: net.ipv4.tcp_max_tw_buckets = 30000net.ipv4.tcp_tw_recycle = 1net.ipv4.tcp_tw_reuse = 1 As well on the server's side look onto result of ulimit -n . Default value is 1024x768 for the limit of Max open files, which can explain appearance of bindexceptions at the connections. As well you can monitor number of connections between the server and jmeter during test-run using e.g. netstat -an | grep SERVER_PORT | wc -l To define limit of connections-if any. ShareImprove this answer Edited Jan 9 ' at 15:30 answered Jan 7 ' at 16:51aliaksandr Belik9,2105

     thanks Belik, Your answer very helpful for me. However, it still not solved by trying them. – pyisoemaw jan 8 ' for 11:44      so, any new Details? If Windows os:same behavior after applying all the Instructions? – aliaksandr belik jan 8 ' at 12:39      i am using CentOS 5 for Apache Server and testing from Windows XP client PC. I have followed the detail procedure of the referenced link. However, it didn ' t work. But I found something so if I changed keepalivetimeout into and httpd.conf file in CentOS server, it does solved the P Roblem. Honestly, I don ' t clearly understand why it's solved by doing it. Do it? – pyisoemaw jan 9" at 3:37 Have you increased or decreased keepalivetimeout value? Please look into the update in answer, I ' ve added several common issues for load-testing using Linux boxes. Maybe something of these point is helpful for you. –aliaksandr Belik Jan 9 ' at 13:03

Time_wait too many workarounds for Linux and Windows