From derby-dev-return-8502-apmail-db-derby-dev-archive=db.apache.org@db.apache.org Mon Sep 19 09:53:00 2005 Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 82124 invoked from network); 19 Sep 2005 09:52:59 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 19 Sep 2005 09:52:59 -0000 Received: (qmail 73731 invoked by uid 500); 19 Sep 2005 09:52:59 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 73487 invoked by uid 500); 19 Sep 2005 09:52:58 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Development" Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 73476 invoked by uid 99); 19 Sep 2005 09:52:58 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=SPF_FAIL X-Spam-Check-By: apache.org Received: from [192.87.106.226] (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Sep 2005 02:52:56 -0700 Received: from ajax.apache.org (ajax.apache.org [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id D78AE125 for ; Mon, 19 Sep 2005 11:52:54 +0200 (CEST) Message-ID: <30329749.1127123574880.JavaMail.jira@ajax.apache.org> Date: Mon, 19 Sep 2005 11:52:54 +0200 (CEST) From: =?UTF-8?Q?=C3=98ystein_Gr=C3=B8vlen_=28JIRA=29?= To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-569) Derby network server is printing connection activity on System.out instead of logging it to derby.log In-Reply-To: <1238576198.1126687734268.JavaMail.jira@ajax.apache.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/DERBY-569?page=3Dcomments#action= _12329819 ]=20 =C3=98ystein Gr=C3=B8vlen commented on DERBY-569: --------------------------------------- The current situation is as follows:=20 - If you use the existing scripts to start a network sever, it is not poss= ible to turn off console output. - If you create your own Java program to start server, you can specify an = alternative output or null. - It is possible to turn off logging of connections to derby.log by settin= g derby.drda.logConnections to false. One solution to this request is to let derby.drda.logConnections also turn = off logging of connections to console.=20 The drawback of this is that it will not satisfy those users who would like= to turn off logging to the console but keep the tracing in derby.log. =20 =20 > Derby network server is printing connection activity on System.out instea= d of logging it to derby.log > -------------------------------------------------------------------------= ---------------------------- > > Key: DERBY-569 > URL: http://issues.apache.org/jira/browse/DERBY-569 > Project: Derby > Type: Bug > Components: Network Server > Versions: 10.0.2.1 > Environment: solaris (but it may not be relevant) > Reporter: Xavier-Francois VIGOUROUX > Priority: Trivial > > All the messages are going to the derby.log file except the connection ac= tivity. For me,tThis information is not > important enough to be logged to console. --=20 This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira