---------------------------------------------------------------- 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!!! ---------------------------------------------------------------- We have a problem of jserv running away (using 100% CPU) and finally stop communicating with the network. I have found using lsof that the socket is in a CLOSE_WAIT state: : # lsof -i:8010 : COMMAND PID USER FD TYPE DEVICE SIZE/OFF INODE NAME : java 9327 gopherm 10u inet 0x603dc3b8 0t0 TCP : localhost:ajpv12 (LISTEN) : java 9327 gopherm 13u inet 0x60f3b780 0t769 TCP : localhost:ajpv12->localhost:50255 (CLOSE_WAIT) I see it talking to port 50255 which I do the same for: : # lsof -i:50255 : COMMAND PID USER FD TYPE DEVICE SIZE/OFF INODE NAME : java 9327 gopherm 13u inet 0x60f3b780 0t769 TCP : localhost:ajpv12->localhost:50255 (CLOSE_WAIT) Since the PIDs are the same it looks like jserv (or perhaps java) is talking to itself through sockets. Questions: Why would it be talking to itself through sockets? Is it some kind of self test/monitoring? Can it be shutoff if so? What would cause it to fail just before closing the socket? PS Are there any search facilities available for searching this lists archives? Thanks Jon Hickmott - Web Admin - The University of Western Ontario. -- -------------------------------------------------------------- Please read the FAQ! <http://java.apache.org/faq/> To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Search Archives: <http://www.mail-archive.com/java-apache-users%40list.working-dogs.com/> Problems?: [EMAIL PROTECTED]
