----------------------------------------------------------------
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 run a high-volume web site on Solaris JServ 1.1, and have occasionally
found extra Java processes hanging out on the JServ boxes.
If our original JServ process has a PID of 1234, the new Java processes
have a parent process ID (PPID) of 1324, indicating that they were somehow
spawned from the original.
We don't have any native code calling 'fork' anywhere, but we do
occasionally call 'Runtime.exec()' to execute a few non-Java programs (e.g.
'uptime'). These exec calls are bracketed by a "try...finally" that calls
'destroy()' on the child process after a certain amount of time if they are
unresponsive.
My best guess is that the 'exec' call may occasionally screw up during its
initialization and leave an untended child JServ process sitting around,
but I can't seem to find a way to verify or prevent that.
Has anyone seen anything like this before? Could this be something in
JServ itself?
--
--------------------------------------------------------------
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]
