We've run into an unexpected troublesome behavior in Tomcat 5.0.30.
We have an installation script that uses the HTTP interface of the
Manager App to install a number of Web applications in one go.
What we've found is that in some cases the Manager app returns OK to
the caller, claiming that the
We use Tomcat with a fronting Web server (Apache) which provides Basic
authentication, so we need to run with 'tomcatAuthentication=false'
in the Ajp13Connector. But we also want to make use of the servlet
roles concept to protect applications (including the Manager app)
from arbitrary access.
The org.apache.tomcat.util.log.SystemLogHandler class (source code in
jakarta-tomcat-connectors-4.1.30) handles, among other things,
capturing of System.out and System.err so that they can be redirected
to an application's log file. It makes use of another class
(CaptureLog) to hold the captured
We're porting part of a ServletExec-based shared-container
infrastructure to Tomcat. One of its features is that when the JVM is
started we redirect its standard output to stdio.out, to capture GC
logging and other JVM-specific messages. ServletExec then arranges for
the stdout and stderr of Web
On Mon, 15 Mar 2004, Shapira, Yoav wrote:
Only if your webapps are bad and use System.out/System.err ;)
You can add swallowOutput=true to your context declarations to make
System.out/System.err output from the webapps go to the localhost log.
(Or the Logger defined for the Context, if you
