----------------------------------------------------------------
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]
