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] Resolved: (DERBY-569) Derby network server is printing connection activity on System.out instead of logging it to derby.log
Date Mon, 01 May 2006 19:35:48 GMT
     [ http://issues.apache.org/jira/browse/DERBY-569?page=all ]
     
Bryan Pendleton resolved DERBY-569:
-----------------------------------

    Resolution: Fixed

Kathey, I agree: this change is not important enough to be worth putting into the 10.1 branch
at this time.

The fix is sufficiently useful in my environment that I am running with the patch, but of
course I can continue to run with a patched version even after we upgrade to 10.1.3 in my
environment.


> 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
>     Assignee: Bryan Pendleton
>     Priority: Trivial
>      Fix For: 10.2.0.0
>  Attachments: derby-569-docs.diff, derby-569.diff, 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