----------------------------------------------------------------
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!!!
----------------------------------------------------------------
> From: Kevin Macclay[SMTP:[EMAIL PROTECTED]]
> Subject: Re: Many JServ threads being made and dying
>
> Did you check out the output from the logs to get more of an idea what's
> happening? Did you try increasing the ApJServVMTimeout parameter in the
> jserv.conf to see if it had any effect?
I've checked mod_jserv, jserv and error and none of them show anything. I
did try increasing ApJServVMTimeout to 30 seconds, and the result was that
for the first 30 seconds everything was fine and then the generate/die thing
started happening like before. It was a good idea, though.
> > Besides, it kinda bites that manually kicking off the JVM doesn't seem
> to
> > get proper classpath info from the wrapper.classpath= lines.
>
> You need to create the CLASSPATH environment variable in your manual jserv
> script, or pass the classpath information to the jvm when you call it with
> the "-classpath" option.
Yeah. If anything, trying to figure this problem out is giving me a good
understanding of the architecture of JServ. (Next step, trying to read the
source.) If I can't solve the problem I'm going to have to write a
JVM-kickoff daemon that scans the jserv.properties file for the wrapper.bin,
wrapper.classpath and the command-line options.
> Kevin
>
Murray Todd Williams
--
--------------------------------------------------------------
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]
