I'd argue that dealing with logging configuration is not newbie stuff. This is probably some of the most poorly implemented technology in the servlet container.
On Tue, Dec 3, 2013 at 3:44 PM, Konstantin Kolinko <knst.koli...@gmail.com>wrote: > 2013/12/3 Tomcat Random <tomcat.ran...@gmail.com>: > > Environment is RHEL6, Tomcat 7.0.42. There is only one webapp. > > > > I'm trying to implement log4j as per the instructions here (skipping step > > 5): > > http://tomcat.apache.org/tomcat-7.0-doc/logging.html#Using_Log4j > > > > Since I'm not using the Manager, I've removed the relevant logging lines > > from CATALINA_HOME/lib/log4j.properties, so it looks like this: > > > > _____________________________ > > log4j.rootLogger=INFO, CATALINA > > (...) > > > 1., 2. > > Either filter by category names, or bundle its own > classloader-specific Log4J configuration with your own web application > (a WEB-INF/classes/log4j.properties file). > > > Seriously, the Log4J documentation and mailing lists are elsewhere, > http://logging.apache.org/log4j/1.2/mail-lists.html > > I'd be best to ask newbie questions there, even though this mailing > list has a log of knowledgeable people that may occasionally help you. > > > > > 3. Get rid of the empty localhost. file. > > > > The configuration snippet that you provided does not have a "cluster" > appender. Thus it does not matches your list of log files. > > Best regards, > Konstantin Kolinko > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
