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=12113>. 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=12113 Log4J ConsoleAppender & System.out.println do not display on console ------- Additional Comments From [EMAIL PROTECTED] 2002-08-29 00:11 ------- Here is the change that was made in the 4.1 Tomcat branch to stdout/stderr logging: For those running unix, stdout/stderr has always gone to catalina.out. On windows this goes to the console. On a production system a web application may be using API's which end up using stdout/stderr for output becuase they aren't aware of the ServletContext log. It is more appropriate for this output which is related to a web application context to get logged to that web application contexts log rather than to the console or catalina.out. This makes it easier to debug problems on a production system. Starting in the 4.1 version the stdout and stderr generated by code running within a web application is now logged to that web applications context log. Another option called "swallowOutput" has been added when configuring a context which allows you to enable or disable this. It will be available after tonights nightly build and in the Tomcat 4.1.10 release. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
