You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Andrew McIntyre (JIRA)" <de...@db.apache.org> on 2005/11/10 22:11:03 UTC
[jira] Resolved: (DERBY-569) Derby network server is printing connection activity on System.out instead of logging it to derby.log
[ http://issues.apache.org/jira/browse/DERBY-569?page=all ]
Andrew McIntyre resolved DERBY-569:
-----------------------------------
Fix Version: 10.2.0.0
Resolution: Fixed
Committed doc updates to trunk with revision 332372.
> 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
> 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