---------------------------------------------------------------- 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!!! ---------------------------------------------------------------- Looking over jserv.conf I found # The amount of time to give to the JVM to start up as well # as the amount of time to wait to ping the JVM to see if it # is alive. Slow or heavily loaded machines might want to # increase this value. # Default: 10 seconds # ApJServVMTimeout 10 which is the likely explanation for the port-scan problem I asked about earlier. None-the-less when I try my netstat -c trick (see previous post), I get 32 (maybe more, the netstat -c may be missing some of them as it refreshes relatively slowly) pings within 2 mins, which is more like a default value of 4 seconds rather than the 10 noted in the config file. Does this need to be updated? What is the rational behind having the httpd daemon ping the JVM every 10 seconds? Regards, Sheer -- -------------------------------------------------------------- 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]
