Return-Path: Delivered-To: apmail-logging-log4j-user-archive@www.apache.org Received: (qmail 29011 invoked from network); 31 Oct 2008 14:44:24 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 31 Oct 2008 14:44:24 -0000 Received: (qmail 18518 invoked by uid 500); 31 Oct 2008 14:44:27 -0000 Delivered-To: apmail-logging-log4j-user-archive@logging.apache.org Received: (qmail 18490 invoked by uid 500); 31 Oct 2008 14:44:26 -0000 Mailing-List: contact log4j-user-help@logging.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Log4J Users List" Reply-To: "Log4J Users List" Delivered-To: mailing list log4j-user@logging.apache.org Received: (qmail 18479 invoked by uid 99); 31 Oct 2008 14:44:26 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 31 Oct 2008 07:44:26 -0700 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 31 Oct 2008 14:43:10 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1KvvE6-00083f-8m for log4j-user@logging.apache.org; Fri, 31 Oct 2008 07:43:50 -0700 Message-ID: <20267368.post@talk.nabble.com> Date: Fri, 31 Oct 2008 07:43:50 -0700 (PDT) From: nknk To: log4j-user@logging.apache.org Subject: All log4j messages are going over the Socket? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: nkunkov@escholar.com X-Virus-Checked: Checked by ClamAV on apache.org Hi, I have a java web application that will be run in a clustered environment. The user would like to consolidate the logs in one file by writing to the socket and then to a central file. I have used the org.apache.log4j.net.SocketServer to listen for incoming log4j messages from the client application. Whatever SocketServer recieves, it will use a regular File appender to write to a central file. Here is my problem - no matter what log level is set in the application and in the properties file for SocketServer, ALL of the log4j messages are comming across the network through the socket. Let's say in the application the level is ERROR and in the properties file that SocketServer is using to write to the file, the level is also ERROR, only ERROR messages will be written to the file, but it looks like all the messages went over the network and SocketServer just filtered the ERROR ones. If I change SocketServer's level to DEBUG, I will see all the DEBUG messages even though Application's level is still set to ERROR. Our application has a lot of DEBUG messages and I'm afraid that all the network traffic will impede preformance. Is there any way around this? Also is there a way to determine that SocketServer is down and stopped logging messages? Do I need to to close the socket appender? Apologies if the questions are trivial.. Thanks for your help -- View this message in context: http://www.nabble.com/All-log4j-messages-are-going-over-the-Socket--tp20267368p20267368.html Sent from the Log4j - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org For additional commands, e-mail: log4j-user-help@logging.apache.org