Separating JVM's stdout from Tomcat's

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

RE: Separating JVM's stdout from Tomcat's

Hi, We'd like to do something similar in Tomcat but it's not clear how to accomplish it. The catalina.sh startup script redirects stdout to catalina.out, but that file ends up capturing both JVM logging and Web application logging. Only if your webapps are bad and use System.out/System.err ;)

Re: Separating JVM's stdout from Tomcat's

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

RE: Separating JVM's stdout from Tomcat's

At 12:23 PM 3/15/2004 -0500, you wrote: Hi, We'd like to do something similar in Tomcat but it's not clear how to accomplish it. The catalina.sh startup script redirects stdout to catalina.out, but that file ends up capturing both JVM logging and Web application logging. Only if your webapps