db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Pendleton (JIRA)" <derby-...@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
Date Thu, 03 Nov 2005 17:24:55 GMT
     [ 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


Mime
View raw message