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 "Kathey Marsden (JIRA)" <de...@db.apache.org> on 2005/11/07 19:14:20 UTC
[jira] Commented: (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=comments#action_12356968 ]
Kathey Marsden commented on DERBY-569:
--------------------------------------
I'll look at committing this patch. A few quick questions/comments first
1) Have you submitted an ICLA yet?
2) Did you run with JCC after all?
The 10.2 documentation should be updated with the new behaviour. Can you update the doc or log a Jira noting the doc locations that need changing?
I think it would be worthwhile mentioning this change in the 10.2 release notes as well. Maybe a separate Jira issue for that would be good so it doesn't get lost for the 10.2 release notes.
> 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