You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2002/09/25 15:56:49 UTC
DO NOT REPLY [Bug 12931] -
Catalina eats System.out.println()
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=12931>.
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=12931
Catalina eats System.out.println()
------- Additional Comments From jakarta@trollingers.com 2002-09-25 13:56 -------
The problem is in the o.a.c.core.StandardWrapper.loadServlet()
Any System.out statements get eaten between
SystemLogHandler.startCapture();
and
SystemLogHandler.stopCapture();
I understand why someone might want this behavior, but I believe that the
redirection of System.out should be controlled by the server admin. I also
think that if you are going to eat System.out of the init and destroy then all
servlet methods should be called in that way. It does not make since to only
redirect init and destroy.
can someone please help me understand why it was done this way before I make
any changes.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>