I don't know how achievable that is. I've encountered many instances where
JDK classes themselves write info to stdout or stderr. Try loading a
truncated JPEG image, for instance, and see what shows up on stdout. (That's
just one example that I can remember off the top of my head.)
My recommendation to you would be to ensure any Java app you launch from
within Java calls System.setOut and System.setErr to replace those streams
with custom Java classes that suppress the output.
> -----Original Message-----
> From: Joseph Panico [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, March 15, 2001 9:15 AM
> To: [EMAIL PROTECTED]
> Subject: irrepressible messages
>
>
> Folks,
>
> We have a requirement that some java processes must run
> without producing
> *any* output on stderr or stdout under any circumstances.
> Unfortunately,
> LogLog prints to stderr in the error method, even if internal
> debugging is
> disabled. We must have the ability to make a JVM "run silent".
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
