Thanks for the reply Andre...responses in line

> -----Original Message-----
> From: André Warnier [mailto:a...@ice-sa.com]
> Sent: 29 October 2009 10:47
> To: users@httpd.apache.org
> Subject: Re: [us...@httpd] Apache Close-Wait ports issue
> 
> Welcome ;-)
> 
> Darren Kukulka wrote:
> >
> > Painting a brief picture ;
> > Several applications running on Tomcat 6.0.19 (64-bit) - several
> cluster
> > groups
> > Backend SQL Server 2005 clustered DBs (several)
> > Front end Apache Web servers (2.2.9 with mod_jk 1.2.19), load
> balanced
> > via secure network appliance
> >
> ...
> > The problem is that all the web servers stop responding to external
> > requests.  Looking at the ports in use on each server...
> .  All of the web servers also have exactly 30 close-wait sessions
> > with the secure network appliance.
> 
> 
> If I get this right, you have
> 
> browsers <--> network appliance <--> Apache httpd servers <--> other
> stuff
> and your CLOSE_WAIT sockets are on the Apache httpd servers, for
> connections with the network appliance, right ?
> 


Correct - the connections from the Web Servers to the Tomcat app servers down 
the line remain established.

> Did you check (with "netstat -pan" e.g.) if that is really the case ?
> 
> If that is correct, it would mean that Apache has closed these sockets,
> but is waiting for the network appliance to close it's side of these
> connections, which never happens.  Any idea why that might be ?
> 
> Another question : when that happens, how many Apache children/threads
> are running ?
> Maybe you just have 30 Apache children/threads that are "stuck" because
> they are waiting for the network appliance to close these sockets, and
> it never happens.
> As long as they would be waiting for that, they would never be recycled
> by Apache to handle new requests, which may explain what you're seeing
> ?
>

So as we're not specifying any directives in the httpd.conf, with respect to 
connection control, the default of KeepAlive=on and KeepAliveTimout=15 applies? 
 Would this not clear out the close-wait connections?

We've queried the network appliance vendor but they are unaware of any reasons 
the appliances would not close the sockets.
 
> 
> 
> ---------------------------------------------------------------------
> The official User-To-User support forum of the Apache HTTP Server
> Project.
> See <URL:http://httpd.apache.org/userslist.html> for more info.
> To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
>    "   from the digest: users-digest-unsubscr...@httpd.apache.org
> For additional commands, e-mail: users-h...@httpd.apache.org



Connaught plc is a FTSE 250 company. We are the UK's leading provider of 
integrated services operating in the compliance, social housing and public 
sector markets.

Please visit our website to see a full list of Connaught's Registered Companies 
www.connaught.plc.uk/group/aboutconnaught/registeredcompanies

Disclaimer:
The information transmitted is intended only for the person or entity to which 
it is addressed and may contain confidential and/or privileged material. Any 
review, retransmission, dissemination or other use of, or taking of any action 
in reliance upon, this information by persons or entities other than the 
intended recipient is prohibited. If you received this in error, please contact 
the sender and delete this message. Connaught plc, Head Office 01392 444546

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
   "   from the digest: users-digest-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org

Reply via email to