-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Timir,

On 4/9/2010 8:10 AM, Timir Hazarika wrote:
> Mark, I'm using netstat as follows. You can see the tomcat process listening
> on 8443 and all the incoming requests in TIME_WAIT. These connections do get
> cleared after the default timeout of 60 seconds, my intention is to refuse
> creating them in the first place.

You can't refuse "creating" a TIME_WAIT socket: it's the result of
handling a socket and then closing it. You might want to review the TCP
connection states here:

http://en.wikipedia.org/wiki/Transmission_Control_Protocol#Protocol_operation

This is not an accept problem, this is a problem with having serviced a
request via a socket and then closing the connection. Given that you
can't avoid accepting connections on a useful web server, you will not
be able to prevent them from going through their natural lifecycle.

- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAku/QWkACgkQ9CaO5/Lv0PC1tACeOPKViy9KHPbK35tqWjmRKB8S
kmUAn0q85D72X0Jep0O/T7yy/brveI/R
=5N1X
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to