That fits with how I understand the configuration. If you include log4j.jar in your war then the classloader will use that jar instead of the jar in common/lib and will use the config in the war also.
On Wed, Jun 4, 2008 at 2:34 PM, Serroul, Carol <[EMAIL PROTECTED]> wrote: > Good afternoon, > > I debated which list to send this to as I'm not sure if it is a tomcat issue > or a log4j one. > > We have a tomcat environment (5.5.25) with log4j-1.2.14.jar located in > common/lib. Each app that we deploy generally has a log4j.properties file to > configure it's own logging. What we've found is that if we don't include the > log4j file in the war file for each application, all of our logging output > goes to tomcat.log. If we deploy a log4j jar file with our war file, the > logging works correctly. > > Have any of you run into anything similar? I can send whatever config files > might be necessary but don't want to pre-emptively flood you with information. > > Thanks! > > Carol Serroul | Senior Systems Analyst | Analyste principal des systèmes > 613-993-2667 | facsimile / télécopieur 613-991-2857 | [EMAIL PROTECTED] > CISTI, National Research Council Canada | 1200 Montreal Road Ottawa ON K1A > 0R6 > ICIST, National Research Council Canada | 1200, chemin Montréal Ottawa ON > K1A 0R6 > Government of Canada | Gouvernement du Canada > > -- James A. N. Stauffer http://www.geocities.com/stauffer_james/ Are you good? Take the test at http://www.livingwaters.com/good/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
