Return-Path: X-Original-To: apmail-tomcat-users-archive@www.apache.org Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4224C18537 for ; Thu, 3 Dec 2015 23:05:41 +0000 (UTC) Received: (qmail 64407 invoked by uid 500); 3 Dec 2015 23:05:38 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 64347 invoked by uid 500); 3 Dec 2015 23:05:37 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 64336 invoked by uid 99); 3 Dec 2015 23:05:37 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Dec 2015 23:05:37 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 630AA180A59 for ; Thu, 3 Dec 2015 23:05:37 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.879 X-Spam-Level: ** X-Spam-Status: No, score=2.879 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id Tj2HsMwSRa_j for ; Thu, 3 Dec 2015 23:05:34 +0000 (UTC) Received: from mail-lb0-f195.google.com (mail-lb0-f195.google.com [209.85.217.195]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id 6D69121231 for ; Thu, 3 Dec 2015 23:05:34 +0000 (UTC) Received: by lblw10 with SMTP id w10so1027938lbl.2 for ; Thu, 03 Dec 2015 15:05:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=kcvy2mrRlA2YkRsSQk2ykm3BCgcvqENlEMOQGvlSBqc=; b=E25Ey3KQgLQcoalQiB1eEnxcMf49Ogf4KZBDJErAbrDf2Cjd8aak9PsqW0VSW6vMUC 8M8yeeLHXn/ZBRwtB9XrD7TpUxCDOFoWplfFebAbaniYFnWtx0JP6WV931k/CZZV90QN 7+DvJi8PrMXYz6yRJ7JqO/8ZzEw9q2lOT0mi7LDu/gDXZkyfQ13qrV/LytErzzMlhN2K C+OJF9eZZG0CbPU5l/V7BIJU+YaHBjwLsb4ogu9a1OIg5pa1j0XAmmFfC2rao+NyAc0m RlB1ESYTDSrRaDPBD0rtT6nkOPQSFxKmycx+f3NfVfyc+9cs4W/BBTvmeGt0EM2p29iZ 6yPw== MIME-Version: 1.0 X-Received: by 10.112.123.208 with SMTP id mc16mr6604635lbb.107.1449183927776; Thu, 03 Dec 2015 15:05:27 -0800 (PST) Received: by 10.112.6.133 with HTTP; Thu, 3 Dec 2015 15:05:27 -0800 (PST) Date: Thu, 3 Dec 2015 18:05:27 -0500 Message-ID: Subject: Understanding how to controlling what data is written to log4j appenders From: Joleen Barker To: Tomcat Users List Content-Type: multipart/alternative; boundary=047d7bfcfbc23abfbb0526066de6 --047d7bfcfbc23abfbb0526066de6 Content-Type: text/plain; charset=UTF-8 I want to have more control over what data is written to the various appenders in the log4j.properties files. I have played around with the various configurations in the log4j.properties file but I am not understanding how they are working in order to grasp how to have more control. I don't know if it would be a matter of turning off the INFO setting for the log4j.rootLogger and somehow setting individual logging for each appender. Below is my environment details: 1) The tomcat version that is running is v8.0.26.0 2) The OS is a Centos v7 UNIX VM 3) Java JDK I have installed that Tomcat is using is 1.8.0_60 4) Due to the catalina.out file growing too large with the default juli.AsyncFileHandler using the logging.properties file that was found in the $CATALINA_HOME/conf directory. I changed the settings on a vendors software to use the log4j logging instead. (So this is NOT my web application or product written by me.) 5) I set the swallowOutput="true" in the vendors .xml file to stop messages for stdout and stderr from going to the catalina.out files. 6) Most messages are now going to the catalina (no extention) and/or the localhost files which are rolled over daily when there is activity. 7) The vendors web application uses the context of cfcc. The Connector details are found in the \server\conf\Catalina\localhost\cfcc.xml 8) I have A LOT of duplication in the log files. I would like to change that if I can. 9) Below are my log4j.properties settings: log4j.rootLogger=INFO, CATALINA # Define all the appenders log4j.appender.CATALINA=org.apache.log4j.DailyRollingFileAppender log4j.appender.CATALINA.File=${catalina.base}/logs/catalina log4j.appender.CATALINA.Append=true log4j.appender.CATALINA.Encoding=UTF-8 # Roll-over the log once per day log4j.appender.CATALINA.DatePattern='.'yyyy-MM-dd'.log' log4j.appender.CATALINA.layout = org.apache.log4j.PatternLayout log4j.appender.CATALINA.layout.ConversionPattern = %d [%t] %-5p %c- %m%n log4j.appender.CFCC=org.apache.log4j.DailyRollingFileAppender log4j.appender.CFCC.File=${catalina.base}/logs/cfcc log4j.appender.CFCC.Append=true log4j.appender.CFCC.Encoding=UTF-8 log4j.appender.CFCC.DatePattern='.'yyyy-MM-dd'.log' log4j.appender.CFCC.layout = org.apache.log4j.PatternLayout log4j.appender.CFCC.layout.ConversionPattern = %d [%t] %-5p %c- %m%n log4j.appender.LOCALHOST=org.apache.log4j.DailyRollingFileAppender log4j.appender.LOCALHOST.File=${catalina.base}/logs/localhost log4j.appender.LOCALHOST.Append=true log4j.appender.LOCALHOST.Encoding=UTF-8 log4j.appender.LOCALHOST.DatePattern='.'yyyy-MM-dd'.log' log4j.appender.LOCALHOST.layout = org.apache.log4j.PatternLayout log4j.appender.LOCALHOST.layout.ConversionPattern = %d [%t] %-5p %c- %m%n log4j.appender.MANAGER=org.apache.log4j.DailyRollingFileAppender log4j.appender.MANAGER.File=${catalina.base}/logs/manager. log4j.appender.MANAGER.Append=true log4j.appender.MANAGER.Encoding=UTF-8 log4j.appender.MANAGER.DatePattern='.'yyyy-MM-dd'.log' log4j.appender.MANAGER.layout = org.apache.log4j.PatternLayout log4j.appender.MANAGER.layout.ConversionPattern = %d [%t] %-5p %c- %m%n log4j.appender.HOST-MANAGER=org.apache.log4j.DailyRollingFileAppender log4j.appender.HOST-MANAGER.File=${catalina.base}/logs/host-manager. log4j.appender.HOST-MANAGER.Append=true log4j.appender.HOST-MANAGER.Encoding=UTF-8 log4j.appender.HOST-MANAGER.DatePattern='.'yyyy-MM-dd'.log' log4j.appender.HOST-MANAGER.layout = org.apache.log4j.PatternLayout log4j.appender.HOST-MANAGER.layout.ConversionPattern = %d [%t] %-5p %c- %m%n log4j.appender.CONSOLE=org.apache.log4j.ConsoleAppender log4j.appender.CONSOLE.Encoding=UTF-8 log4j.appender.CONSOLE.layout = org.apache.log4j.PatternLayout log4j.appender.CONSOLE.layout.ConversionPattern = %d [%t] %-5p %c- %m%n # Configure which loggers log to which appenders log4j;logger.org.apache.catalina.core,ContainerBase.[Catalina].[localhost].[/cfcc]=INFO, CFCC log4j.logger.org.apache.catalina.core.ContainerBase.[Catalina].[localhost]=OFF, LOCALHOST log4j.logger.org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/manager]=\ INFO, MANAGER log4j.logger.org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/host-manager]=\ INFO, HOST-MANAGER At this time ALL the same messages are written to the cfcc and the localhost log files. Absolutely no difference. All the messagse that are written to these two logs are also in the catalina log alongs with the tomcat startup messages. I would like to separate the tomcat startup messages from the web application messages that are written to both the localhost and cfcc logs. Thank you for your help in advance. -Joleen --047d7bfcfbc23abfbb0526066de6--