Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 50639 invoked from network); 14 Sep 2005 08:01:20 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 14 Sep 2005 08:01:20 -0000 Received: (qmail 20358 invoked by uid 500); 14 Sep 2005 08:01:18 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 20334 invoked by uid 500); 14 Sep 2005 08:01:18 -0000 Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Discussion" Delivered-To: mailing list derby-user@db.apache.org Received: (qmail 20320 invoked by uid 99); 14 Sep 2005 08:01:18 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Sep 2005 01:01:18 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [192.18.98.34] (HELO brmea-mail-3.sun.com) (192.18.98.34) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Sep 2005 01:01:28 -0700 Received: from phys-epost-1 ([129.159.136.14]) by brmea-mail-3.sun.com (8.12.10/8.12.9) with ESMTP id j8E81A1L004559 for ; Wed, 14 Sep 2005 02:01:11 -0600 (MDT) Received: from conversion-daemon.epost-mail1.sweden.sun.com by epost-mail1.sweden.sun.com (iPlanet Messaging Server 5.2 HotFix 1.24 (built Dec 19 2003)) id <0IMS00J01R9T5O@epost-mail1.sweden.sun.com> (original mail from Oystein.Grovlen@Sun.COM) for derby-user@db.apache.org; Wed, 14 Sep 2005 10:01:10 +0200 (MEST) Received: from atum11.norway.sun.com.sun.com (atum11.Norway.Sun.COM [129.159.112.211]) by epost-mail1.sweden.sun.com (iPlanet Messaging Server 5.2 HotFix 1.24 (built Dec 19 2003)) with ESMTP id <0IMS000YBRLX67@epost-mail1.sweden.sun.com> for derby-user@db.apache.org; Wed, 14 Sep 2005 10:01:10 +0200 (MEST) Date: Wed, 14 Sep 2005 10:01:08 +0200 From: Oystein.Grovlen@Sun.COM (=?iso-8859-1?q?=D8ystein_Gr=F8vlen?=) Subject: Re: suppress "connection %d" message on console In-reply-to: <4326E157.8010808@sbcglobal.net> To: Derby Discussion Message-id: MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 8BIT User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.2 Lines: 33 References: <4326E157.8010808@sbcglobal.net> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N >>>>> "KM" == Kathey Marsden writes: KM> �ystein Gr�vlen wrote: >>>>>>> "XV" == Xavier Vigouroux writes: >>>>>>> >>>>>>> >> XV> hi, XV> is there a way to remove the message on console indicating new XV> connection to the server ? >> >> As far as I can see from the code, these messages will always go to >> System.out. Please file a JIRA issue if you want this to change. >> >> >> KM> You could specify an alternate console PrintWriter with KM> NetworkServerControl.start (null will suppress output) or use the KM> derby.drda.startNetworkServer property to start the server and then the KM> console output will go to derby.log. If I understand this correctly, both these options requires that you create your own java program in order to start the network server. If you invoke NetworkServerControl.main (as the provided scripts do), it does not seem to be any way to turn off the console output. Anyhow, your solution will turn off all console output. The request was to be able to turn off logging of new connections. In my opinion, the logConnections property should affect both console output and output to the derby.log file. -- �ystein