http://publib.boulder.ibm.com/infocenter/initiate/v9r5/index.jsp?topic=%2Fcom.ibm.inspinstall.doc%2Ftopics%2Ft_inspinstall_configuring_log4j_logging_apachetomcat.html
Having the logging items in the shared/lib means that the shared/classes needs to have a log4j.properties file. I dropped one of my log4j.properties files into that directory, and I was able to pipe log output there...anyone know how I can have a separate one for each app, so that the logfiles will be readable and not all mangled together? Outside of editing all the modules to use a named logger... -- Chris On Tue, Mar 13, 2012 at 3:53 PM, Christopher Gross <cogr...@gmail.com> wrote: > Allen -- Is there something in particular that your users need to do > for the common logging? Any changes in the file or the setup of their > web app? > > An example of the log4j.properties file from a WEB-INF/classes dir: > > log4j.appender.A1=org.apache.log4j.DailyRollingFileAppender > log4j.appender.A1.layout=org.apache.log4j.PatternLayout > log4j.appender.A1.layout.ConversionPattern=%d %-5p %c - %m%n > log4j.appender.A1.File=/test/logs/app/console.log > > log4j.appender.AppAppender=org.apache.log4j.DailyRollingFileAppender > log4j.appender.AppAppender.layout=org.apache.log4j.PatternLayout > log4j.appender.AppAppender.layout.ConversionPattern=%d %-5p %c - %m%n > log4j.appender.AppAppender.File=/test/logs/app/app.log > > log4j.rootLogger=WARN, A1 > log4j.logger.opensearch=DEBUG,AppAppender > > -- Chris > > > > On Tue, Mar 13, 2012 at 3:43 PM, Allen Reese <are...@yahoo-inc.com> wrote: >> We have people exclude commons-logging, and log4j as our installation >> provides them for you in a common lib dir. >> >> --Allen Reese >> Yahoo!, Inc. >> >>> -----Original Message----- >>> From: Christopher Gross [mailto:cogr...@gmail.com] >>> Sent: Tuesday, March 13, 2012 12:41 PM >>> To: Tomcat Users List >>> Subject: Tomcat Logging Jarhell >>> >>> Hi all. >>> >>> I'm trying to utilize the common/lib and shared/lib directories on >>> Tomcat 5.5.25. I have a few separate apps that were each using many of >>> the same JAR files, so I have been moving them down to shared & common >>> lib (DB stuff went to common/lib, the apache commons modules & others >>> went to the shared/lib). I was doing testing as I went along >>> -- but I never went to look at the logfiles for my webapps. I'm now >>> noticing that they aren't getting anything anymore. I haven't changed >>> anything aside from moving the JARs around. I'm using the Apache Log4j >>> Logger in my classes. >>> >>> I have: >>> shared/lib: >>> commons-logging-1.0.4.jar >>> commons-logging-api.jar >>> commons-logging.jar >>> >>> common/lib: >>> apache-log4j-extras-1.0.jar >>> log4j-1.2.15.jar >>> >>> each app has: >>> commons-logging-1.0.4.jar >>> commons-logging-api.jar >>> commons-logging.jar >>> >>> I'd like to avoid rolling back to how everything was, with a lot of >>> repeated JAR files all over the place. Has anyone run into a similar >>> problem and found a decent solution? >>> >>> Any help/tips are appreciated. >>> >>> Thanks! >>> >>> -- Chris >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >>> For additional commands, e-mail: users-h...@tomcat.apache.org >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: users-h...@tomcat.apache.org >> --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
