Re: [Wrapper-user] requestThreadDump and log4j

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

Sal,
    I started to implement some code to make the user use the Original 
System.out
even if the application overrides it.  But I stopped to think that doing 
so would
remove control over the Wrapper's output from the application.  As 
things are, the
user code has the option to redirect System.out if they choose.

    The patch that I applied to remove the log output from the 
requestThreadDump
method would still be valid either way.  Even if I was writing to the 
original
PrintStream rather than the application replaces Stream, there would 
still be a
chance of this leading to a hang.   The message was not really needed 
anyway.

Cheers,
Leif

Sal Ingrilli wrote:

>if at initialization the wrapper does this:
>PrintStream mySystemOut = System.out;
>
>then it can still log to the original System.out by doing this:
>mySystemOut.println () instead of System.out.println ()
>
>this way the wrapper doesn't need to sacrifice its own logging statements.
>
>meanwhile, everybody else that uses System.out ends up going through log4j
>because log4j probably did System.out = new Log4JPrintStream ();
>  
>