----------------------------------------------------------------
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!!!
----------------------------------------------------------------
Oh.
You mean jserv queries the JVM with some sort of "no op" just to make sure
the JVM is still hanging around and listening? And it does this every few
seconds, so that if for whatever reason the JVM goes down (and doesn't
respond), jserv will know to start it back up?
If that's the case, all makes sense now. A few months ago I would have
complained that it was an ugly solution to the problem, but having had to
write a couple client-server apps from scratch, I know better.
Hmm. I'm just about to finish writing a daemon that does the JVM
instantiation and listens to SIGCHLD, SIGHUP and SIGKILL to respond
appropriately. The only thing it doesn't do is check to see if a connection
can be made to 8007.
Interesting...
Murray
> ----------
> From: Marc Slemko[SMTP:[EMAIL PROTECTED]]
> Reply To: Java Apache Users
> Sent: Thursday, May 11, 2000 1:39 PM
> To: Java Apache Users
> Subject: RE: Many JServ threads being made and dying
>
> ----------------------------------------------------------------
> 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!!!
> ----------------------------------------------------------------
>
> On Thu, 11 May 2000, Williams, Murray Todd wrote:
>
> > > jserv automatically connects to the JVM to verify that it is up
> > > and running and happy. This is not done if you start the JVM
> > > manually, since then it is your problem to ensure it is running
> > > properly.
> > >
> > > This seems to explain everything you see without there being any
> > > "problem".
> > The "problem" is that the behavior of Apache JServ as a server process
> > differs depending on whether I (a) let JServ start up the JVM as is the
> > default configuration or (b) I start the JVM manually.
> >
> > If I start the JVM manually, I do NOT have over 300 JVM threads created
> and
> > destroyed every hour regardless of whether any requests have been
> processed
> > and I do NOT constantly have 10 or so TCP connections timing-out in the
> > TIME_WAIT state.
>
> Please read what I wrote above that explains this completely. "jserv
> automatically connects to the JVM to verify that it is up and running and
> happy". Those are requests to the JVM. Then read what I said next: "This
> is not done if you start the JVM manually, since then it is your problem
> to ensure it is running properly." I'm not sure what else I can say if
> you don't want to listen...
>
> I have no idea why you are concerned about a couple of hundred threads an
> hour, that is a completely inconsequential number.
>
> >
> > This is one of those particularly frustrating problems because it
> doesn't
> > really seem to cause noticable operational problems with the server
> > (although I can't guess if there might be some subtle side-effects) so
> it
> > has managed to go on this long ignored.
>
> Many problems are frustrating if you think that anything you don't
> understand must be a problem and you are horrified at how long this
> "problem" has been ignored, and if you refuse to listen to explanations
> of what is going on.
>
>
>
> --
> --------------------------------------------------------------
> 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]
>
--
--------------------------------------------------------------
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]
