Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 31966 invoked from network); 3 Nov 2005 17:25:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 3 Nov 2005 17:25:18 -0000 Received: (qmail 83935 invoked by uid 500); 3 Nov 2005 17:25:17 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 83694 invoked by uid 500); 3 Nov 2005 17:25:16 -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: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 83685 invoked by uid 99); 3 Nov 2005 17:25:16 -0000 X-ASF-Spam-Status: No, hits=1.3 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; Thu, 03 Nov 2005 09:25:16 -0800 Received: from ajax.apache.org (ajax.apache.org [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id 9273E23E for ; Thu, 3 Nov 2005 18:24:55 +0100 (CET) Message-ID: <402577588.1131038695596.JavaMail.jira@ajax.apache.org> Date: Thu, 3 Nov 2005 18:24:55 +0100 (CET) From: "Bryan Pendleton (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Updated: (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: 7bit 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=all ] Bryan Pendleton updated DERBY-569: ---------------------------------- Attachment: svn2.diff Attached is a patch to the current trunk implementing the change that Oystein suggested: placing the trace message under the control of derby.drda.logConnections property. I have tested the change by hand, and also run derbyall successfully. Two test output files needed to be changed to reflect that the trace message is no longer printed. Please review this change and commit if appropriate. Thanks! > Derby network server is printing connection activity on System.out instead 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 > Attachments: svn2.diff > > All the messages are going to the derby.log file except the connection activity. For me,tThis information is not > important enough to be logged to console. -- 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