Thanks. This should work. I hope there was better logging infrastructure in terms of compressing the file, ftp, log service, archival etc.
Nishant On Tue, Sep 22, 2009 at 8:35 PM, Christopher Schultz <ch...@christopherschultz.net> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Jeffrey, > > On 9/22/2009 11:00 AM, Jeffrey Janner wrote: >> My solution was to put log4j.jar in WEB-INF/lib of each instance, along >> with individual log4j.properties files and setting different file paths >> in the properties files. Only solution I could find. > > I believe this is the best solution to this problem. It allows the > webapp to have control over its own logging, which is nice. You can > package a log4j.properties file along with your webapp and configure it > however you like. > > - -chris > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (MingW32) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iEYEARECAAYFAkq4558ACgkQ9CaO5/Lv0PDwdACgkBeSmO2gU+YFXrgKNL/P4/0I > VxMAniVkA4PKQPNaXhXxuy4ViK7gJ/mo > =CC3S > -----END PGP SIGNATURE----- > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > -- Nishant Chandra Hyderabad, India Cell : +91 9949828480 --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
