tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 18462] - System.err gets overriden to output to System.out
Date Wed, 23 Apr 2003 15:22:06 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18462>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18462

System.err gets overriden to output to System.out





------- Additional Comments From glenn@apache.org  2003-04-23 15:22 -------
Without the SysteLogHandler and the way it redirects System.out and System.err
to the appropriate tomcat log debugging web application problems on a 
production server where you have 20-30 different web applications with
multiple virtual hosts is a nightmare.  There are too many supporting API's
being used in web applicaitons which don't know they are running in a container
and will print stack traces, etc. to System.out or System.err.  Having output
from the same applicaiton in different logs, or output from multiple applications
in the same log because they are printing to System.out or System.err is a pain.

I will not make the change recommended by the patch.

As I said earlier

"You might consider researching this further and submitting a patch
that will work for both cases.  Perhaps a test to not execute the code
if Tomcat is running embedded.  Or a new attribute to disable this."

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message