We have 2 webservers which are running a couple of jobs. I do not know how
they are structured or what they do. After a couple of days the connectivity
to the database is lost, rather new connections cannot be established.
Upon further investigation, I find that netstat -nao shows 2000+ ports open
and in a CLOSE_WAIT state. Since the foreign port is 80, I assume that the
application that is running on server xxx.25.3.3 is talking to the webserver
on xxx.25.4.4.
Could someone shed some light on why these sockets would end up in a
CLOSE_WAIT state. Is there any way, I can set this to Timeout sooner or
autoclose. After a couple of days, I can't even get TNSPing to work anymore.
Proto Local Address Foreign Address State
PID
TCP xxx.25.3.3:4770 xxx.25.4.4:80 CLOSE_WAIT 4016
TCP xxx.25.3.3:4771 xxx.25.4.4:80 CLOSE_WAIT 4016
TCP xxx.25.3.3:4797 xxx.25.4.4:80 CLOSE_WAIT 2988
TCP xxx.25.3.3:4798 xxx.25.4.4:80 CLOSE_WAIT 2988
TCP xxx.25.3.3:4800 xxx.25.4.4:80 CLOSE_WAIT 2984
TCP xxx.25.3.3:4801 xxx.25.4.4:80 CLOSE_WAIT 3140
TCP xxx.25.3.3:4802 xxx.25.4.4:80 CLOSE_WAIT 2984
TCP xxx.25.3.3:4803 xxx.25.4.4:80 CLOSE_WAIT 3140
TCP xxx.25.3.3:4804 xxx.25.4.4:80 CLOSE_WAIT 2744
TCP xxx.25.3.3:4805 xxx.25.4.4:80 CLOSE_WAIT 2744
TCP xxx.25.3.3:4806 xxx.25.4.4:80 CLOSE_WAIT 2872
TCP xxx.25.3.3:4807 xxx.25.4.4:80 CLOSE_WAIT 2872
TCP xxx.25.3.3:4808 xxx.25.4.4:80 CLOSE_WAIT 2988
TCP xxx.25.3.3:4809 xxx.25.4.4:80 CLOSE_WAIT 2988
Regards,
Trevor Benedict
MCSD
|