Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 933
  • Last Modified:

CLOSE_WAIT status slowing down my web service?

Hi,

I have a web server running WIN2K. iPlanet Web Server Enterprise Edition 6.0. A lots of my clients/users are complaining that there is a dramatic reduce in speed connecting to my web server. Sometime, they cant even get the page. I did a netstat n and I saw a lot of  CLOSE_WAIT status (more than 100). I suppose it took up a lot of my servers resources When I did a reboot on the web server, the CLOSE_WAIT status are gone and the connection speed to my server resume.

Can anyone please advise me if there is any way I can kill the service and how do I reduce the number of CLOSE_WAIT status? Or is there a way to configure the parameter as to increase the performance of my web server?

I will appreciate for all the advice given. Thanks
0
angls
Asked:
angls
  • 2
1 Solution
 
BigRatCommented:
What web server? IIS or Apache?
0
 
anglsAuthor Commented:
It is iPlanet Web Server Standard Edition 6.0
0
 
BigRatCommented:
Hmmm. The CLOSE_WAIT status is a state in which a socket goes waiting for the other end to also close the socket. It also waits in case any lost packets arrive, since the packet is destined for a port which might get reused and hence the new owner would get an unsolicited message.

Now, the number of ports available for backward connections (which is the majority of these close-wait sockets) is around 24,000 (16 bit port number of which those below 8K don't get used), so you won't run out of those. Each socket under Unix becomes effectively a file descriptor so the number of open files (Kernel parameter) should be made as high as possible.

That said however, the normal situation is that a listener (like INet) wakes up a process and passes the incomming connection to it. This process then produces the response and closes the connection.

It is very unlikely that an incomming connection cannot be allocated a socket number since they are all in close-wait. It is more likely that there is no process available to process the connection, since they are all busy dealing with other connections.

I would suggest that you post a question regarding "How to optimise my IPlanet Web Server", since there are people here who have dones such things. I very much doubt that it is a socket problem.

HTH
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now