Forum Discussion
16 years ago
Hi all,
"Connection reset" occurs in the server side means the server machines can't handle the request connection come in because the entire of the connections pool in server side has been used up (every request will use a new connection and will return to the connection pool to the jetty when the request is done).
So, for windows itself, we need to enlarge the "MaxUserPort" of it and better reduce the "TcpTimedWaitDelay" value.
For app server, like Jetty for SoapUI, we also need to enlarge the thread number for it. Now , for jetty , it's default maxThreads number is 250.
Also, I use Jmeter as the load testing tools and enable the "keep alive" for each load request so it will open only one request for each when the load is large.
Regards
Vance
"Connection reset" occurs in the server side means the server machines can't handle the request connection come in because the entire of the connections pool in server side has been used up (every request will use a new connection and will return to the connection pool to the jetty when the request is done).
So, for windows itself, we need to enlarge the "MaxUserPort" of it and better reduce the "TcpTimedWaitDelay" value.
For app server, like Jetty for SoapUI, we also need to enlarge the thread number for it. Now , for jetty , it's default maxThreads number is 250.
Also, I use Jmeter as the load testing tools and enable the "keep alive" for each load request so it will open only one request for each when the load is large.
Regards
Vance