|
From: Leif M. <le...@ta...> - 2004-10-06 03:07:11
|
Gil,
I did some testing with a JVM that basically just thrashes output to
the console, and the
Wrapper process does indeed appear to be the bottleneck in this case.
This is caused by
the way the Wrapper is currently logging the output to its log file.
It is only an issue when
there is such very large quantities of console output. I'll take a look
at improving this
performance for the next release. 3.1.2 is currently going through the
final release cycle.
So it will have to wait for the following version.
Cheers,
Leif
Gil Adam wrote:
> I've been trying to test the wrapper 3.1.1 to run Tomcat 5 as a
> Windows NT Service. Our application produces a lot of output to
> STDOUT and when I run it under the Java Service Wrapper with logging
> to a file turned on, the wrapper.exe takes up 100% CPU for a while
> just to process the STDOUT output while the JVM java.exe takes up
> nothing.
>
> I've tried checking to make sure that console logging is off by
> setting the following:
>
> wrapper.ntservices.interactive=false
> wrapper.syslog.loglevel=NONE
> wrapper.console.format=
> wrapper.console.loglevel=NONE
>
> I currently have wrapper.logfile.loglevel=INFO
>
> Does anyone have any experience with this? Other than this one thing,
> the wrapper is working fantastically.
>
> -Gil
|