[EMAIL PROTECTED] wrote:

-----Original Message-----
From: Remy Maucherat [mailto:[EMAIL PROTECTED]]
There's a puzzling side effect to procrun, though: Ant fails to start the Java compiler in "fork" mode. If I disable forking javac, it works. Does the Java process lose the right to fork other processes when it is run through procrun ?
That would be really weird, because the JNI based JavaService didn't have that problem (AFAIK).


Try running in console mode: "procrun.exe //TS//Tomcat5".
That's with the GT option. Does that make a difference ?
I'll check it more (but right after I fix a minor bug in the mapper).

If that's OK then it's a security issue thought. Also what Java and OS?
Mine is Sun's 1.4.1 and WIN2K Server.
1.4.1 + XP

I'm running TC 4.1.20 and web.xml has set:

<init-param>

  <param-name>development</param-name>

  <param-value>false</param-value>

</init-param>
I'm using the fork init-param to fix it:

<init-param>
  <param-name>fork</param-name>
  <param-value>false</param-value>
</init-param>

The error page is the one you get when the compiler is not found.

For each jsp I see that the javac is launched under SYSTEM account. So
it works.
Didn't test with 5.0 but I think that there isn't much difference for
that case.


There is other problem with the running TC using redirected Java, and
that is the
lack of gracefull shutdown option. I'm working on that right now.
It will enable JVM invocation of Bootstrap with (stop or stopd) in that
case if enabled.
It's ok if it just sends a term signal to the VM (there's a shutdown hook).

Remy


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to