[ http://issues.apache.org/jira/browse/DERBY-569?page=all ]
Bryan Pendleton updated DERBY-569:
----------------------------------
Attachment: derby-569.diff
derby-569-docs.diff
Attached is an updated code diff against the current trunk. It is the same as
the previous code diff but it includes a change to trunk/CHANGES as suggested
by Kathey to restart the CHANGES file for Derby 10.2 and to include a note
about this change.
Also attached is a docs diff; I took a stab at adding a note about the new
behavior of derby.drda.logConnections to the two relevant places.
> 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: 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
