tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vinicius Carvalho <>
Subject Yet another swallowOutput question
Date Fri, 18 Sep 2009 18:50:24 GMT
Hello there! I'm trying to redirect some legacy System.out calls in
our app to a different logger. Since tomcat's logging implementation
does not allow one to configure the maximum size of the catalina.out,
we are easily reaching gigabytes of space on that file.

I thought that by just adding:

 <Host name="localhost"  appBase="webapps"
            unpackWARs="true" autoDeploy="true"
            xmlValidation="false" xmlNamespaceAware="false"

Would solve my problems, but, after re-starting the server and calling
a servlet that deliberate calls system.out, the catalina out gets all
the output

Well, tried to configure log4j as explained on, did not work as
well, not matter what I do, catalina.out continues to grow. I do know
that we *should* not have any system.out on our code, but as I said,
it's a legacy code and I can't refactor an entire app in time.

Any ideas on how can one avoid the sysout gets logged?


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message