Hi,
1] having one project in webapps, which will hold connection for 45 seconds.
2] I executed 5000 CURL request, on above project.
3] And then from Clinet Side, from where, I execute curl, kill all curl
process.
So, on server all ESTABLISHED becomes, CLOSE_WAIT in netstat.
tcp0
On 18 Nov 2011, at 08:49, Chandrakant Solanki
solanki.chandrak...@gmail.com wrote:
Hi,
1] having one project in webapps, which will hold connection for 45 seconds.
2] I executed 5000 CURL request, on above project.
3] And then from Clinet Side, from where, I execute curl, kill all curl
3] And then from Clinet Side, from where, I execute curl, kill all curl
process.
So, on server all ESTABLISHED becomes, CLOSE_WAIT in netstat.
I'd imagine kill -KILL or kill -TERM is preventing proper socket
teardown. The server is expecting ACKs from the clients that
apparently not being
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chandrakant,
This is a bit OT from your original question:
On 11/18/11 2:34 AM, Chandrakant Solanki wrote:
Connector port=8080 protocol=org.apache.coyote.
http11.Http11NioProtocol maxThreads=5000 minSpareThreads=100
maxSpareThreads=300
Hi All,
I am using apache-tomcat 6.0.26 and below is my server.xml
Connector port=8080 protocol=org.apache.coyote.
http11.Http11NioProtocol
redirectPort=8443 maxKeepAliveRequests=1
maxThreads=5000 minSpareThreads=100
maxSpareThreads=300
On 18 Nov 2011, at 07:34, Chandrakant Solanki
solanki.chandrak...@gmail.com wrote:
Hi All,
I am using apache-tomcat 6.0.26 and below is my server.xml
Connector port=8080 protocol=org.apache.coyote.
http11.Http11NioProtocol
redirectPort=8443 maxKeepAliveRequests=1