----------------------------------------------------------------
BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
WHEN YOU POST, include all relevant version numbers, log files,
and configuration files. Don't make us guess your problem!!!
----------------------------------------------------------------
Michael,
Are you sure the sockets are in CLOSE_WAIT? or are they
in TIME_WAIT?
Are your clients connecting directly to apache, or are they
going through some kind of firewall/proxy s/w? If so, the
problem may be with the firewall/proxy s/w.
We had/have a similar problem. We traced our problem to the
proxy software running on our firewall. Our clients would
connect to the server via a content mgmt s/w
The problem was that the proxy s/w wouldn't close the
connection properly after it was done, leaving the
sockets on the apache/jser server in TIME_WAIT.
Note: If the connection to apache gets stuck in TIME_WAIT,
so does the connection b/w apache and jserv.
On Solaris a socket in TIME_WAIT expires in 2 minutes. On
linux it may be 30 seconds, but I am not sure.
Our site is a relatively low load one, so we are able to
limp along by bumping up descriptors to a high value
(1024).
The best solution is to fix the proxy s/w, obviously :)
Hope this helps,
naeem
-----Original Message-----
From: Michael Amster [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 28, 1999 10:53 AM
To: [EMAIL PROTECTED]
Subject: Sockets stuck in CLOSE_WAIT state with JServ
----------------------------------------------------------------
BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
WHEN YOU POST, include all relevant version numbers, log files,
and configuration files. Don't make us guess your problem!!!
----------------------------------------------------------------
Hi:
It's me again and we're having a number of problems in the production
environment. We have tried both Apache JServe1.1b3 and the daily build,
but we end up with a number of sockets in CLOSE_WAIT state after running
for a night. The system is using JServ load balancing. Right now our
solution is to restart the JVM periodically and this just won't work.
The configuration again:
2 Intel RH6.1 Servers running Apache 1.3.9 and the jserv module.
2 Sun e250 running Solaris 7, JDK 1.1.8_09a production, Apache JServ
1.1b3/daily (both don't work in this regard)
After running for a while, a netstat will reveal sockets between the
Apache Server and the JVM stuck in the close_wait state. We have
configured jserv for 50 connections, so it will run until all are taken.
Has anyone else tested this stuff with a Linux front end and Sparc
Solaris 7 backend?
Bueller?
-MA
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
