Re: [Wrapper-user] is it possible to disable the console logging?

[Leif M. <le...@ta...>]

Daniel,
Yes, this is possible, you can completely disable logging in a couple of 
ways.

1) Clear the logfile name as follows.  Due to bug in older versions, you 
must use
3.1.1 or above to do this.
wrapper.logfile=

2) Set the logfile loglevel to a high value.  NONE disables it all.
wrapper.logfile.loglevel=NONE

That said however, if you are using a logging system, I would suggest 
that you
take a different approach.   I'm not sure which system you are using, 
but I suggest
that you use your logging system to disable the console output of your 
logging tool
from within the JVM.

The benefit of this approach is that you will still be able to record 
startups, shutdowns,
crash logs, etc. in the wrapper.log file.   If you ever have you 
application suddenly crash
for some reason, you are going to wish you had a record of some kind.   
The Wrapper
is able to log lots of information that is impossible from within the 
JVM because it is
dumped by the JVM at a very low level.

Another approach is to simply guarantee that your wrapper.log files are 
kept small.  By
setting the following, you will tell the Wrapper to roll the log file at 
1MB.  And then keep
the most resent rolled file.  You won't use up much disk space, but you 
will have a record
of what when wrong if the app crashes or restarts.
wrapper.logfile.maxsize=1mb
wrapper.logfile.maxfiles=1

Cheers,
Leif

Daniel Bress wrote:

> I have an application that provides all of its own logging.  I even 
> override the standard out and error print streams to also log to my 
> log files.  Therefore the fact that the service wrapper captures all 
> my console output and logs it to its own file is somewhat redundant.  
> Is there a way to disable this feature?
>
>  
>
> Thanks in advance,
>
> Dan
>