----------------------------------------------------------------
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!!!
----------------------------------------------------------------
After updating to the latest ApacheJserv 1.1-b3 on both my environments
(RedHat 6.2 and Solaris 7) I'm noticing that each request between
mod_jserv and the servlet engine results in a TCP TIME_WAIT state upon
completion of the request indicating that the socket is not being closed
correctly. Everything functions just fine (requests are processed
correctly) but I end up with a lot of resources getting used up for no
good reason. I'm sure it's something in my configuration but the hell if
I can find it; I've configured many 0.9x versions of JServ with no
problems. I've even commented out the 3 second interval PING message in
java_wrapper_unix.c just to reduce the volume of socket errors but
obviously this is not a solution.
I have turned on every log channel I can but no joy. ApacheJServ itself
seems to be a happy camper.
My environment:
RedHat Linux 6.2/Solaris 7
ApacheJServ 1.1-b3
Java 1.2.2 on Linux/Java 1.2 on Solaris
Apache 1.3.9 w/DSO support
Thanks for any insights you might have.
--
--------------------------------------------------------------
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]
