Turns out the multiple / in the context path wasn't a problem. However, its not capturing the System.out and System.err associated with the webapps. An empty file is created, but the System. stuff keeps going to Catalina.out. And i've set the swallowOutput attribute to true, so that functionality isn't working either.
And it's not a issue with the multiple / , I have a single / context path which I know for certain is throwing errors. I changed it to also log individually but it too just generates a an empty file. I'm using Tomcat 5.5.17 on Linux. I've added AccessLogValves to several of my webapps and they work great, too bad no one has developed a SystemErrorLogValve. The java.util.logging section of http://tomcat.apache.org/tomcat-5.5-doc/logging.html seems to indicate that it is possible to capture the System.out stuff to separate files, but apparently this isn't working. The log4j section of the same page seems rather daunting, and I don't know if that will work either. On Fri, Jun 20, 2008 at 10:39 AM, Caldarale, Charles R < [EMAIL PROTECTED]> wrote: > > From: Christopher Schultz [mailto:[EMAIL PROTECTED] > > Subject: Re: Logging contexts with multiple / in path attribute > > > > Does this really capture use of System.out and System.err? Cool! I > > didn't know that! > > Isn't that just a result of setting swallowOutput to "true" for the > <Context>? > > - Chuck > > > THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY > MATERIAL and is thus for use only by the intended recipient. If you received > this in error, please contact the sender and delete the e-mail and its > attachments from all computers. > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
