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 "Xavier-Francois VIGOUROUX (JIRA)" <de...@db.apache.org> on 2005/09/14 10:48:54 UTC
[jira] Created: (DERBY-569) Derby network server is printing connection activity on System.out instead of logging it to derby.log
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
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
[jira] Commented: (DERBY-569) Derby network server is printing connection activity on System.out instead of logging it to derby.log
Posted by "Øystein Grøvlen (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-569?page=comments#action_12329819 ]
Øystein Grøvlen commented on DERBY-569:
---------------------------------------
The current situation is as follows:
- If you use the existing scripts to start a network sever, it is not possible to turn off console output.
- If you create your own Java program to start server, you can specify an alternative output or null.
- It is possible to turn off logging of connections to derby.log by setting derby.drda.logConnections to false.
One solution to this request is to let derby.drda.logConnections also turn off logging of connections to console.
The drawback of this is that it will not satisfy those users who would like to turn off logging to the console but keep the tracing in derby.log.
> 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
>
> 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
[jira] Assigned: (DERBY-569) Derby network server is printing connection activity on System.out instead of logging it to derby.log
Posted by "Bryan Pendleton (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-569?page=all ]
Bryan Pendleton reassigned DERBY-569:
-------------------------------------
Assign To: Bryan Pendleton
> 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
[jira] Resolved: (DERBY-569) Derby network server is printing
connection activity on System.out instead of logging it to derby.log
Posted by "Bryan Pendleton (JIRA)" <de...@db.apache.org>.
[ 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
[jira] Commented: (DERBY-569) Derby network server is printing connection activity on System.out instead of logging it to derby.log
Posted by "Jean T. Anderson (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-569?page=comments#action_12356991 ]
Jean T. Anderson commented on DERBY-569:
----------------------------------------
Doc source for the Derby manuals is in https://svn.apache.org/repos/asf/db/derby/docs/trunk/ . Files are in DITA xml format. More info is at http://db.apache.org/derby/manuals/dita.html .
> 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
[jira] Updated: (DERBY-569) Derby network server is printing connection activity on System.out instead of logging it to derby.log
Posted by "Bryan Pendleton (JIRA)" <de...@db.apache.org>.
[ 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
Re: [jira] Commented: (DERBY-569) Derby network server is printing
connection activity on System.out instead of logging it to derby.log
Posted by Kathey Marsden <km...@sbcglobal.net>.
Kathey Marsden wrote:
>Well thinking about it a bit I'd say let's not:
>
>
>
Oops this was not meant to be part of my previous mail. It just got
left straggling on the bottom.
As the text said originally, if you think it adds more value than
confusion and want to document in the release notes and no one else has
concerns it could go by lazy consensus.
Kathey
Re: [jira] Commented: (DERBY-569) Derby network server is printing
connection activity on System.out instead of logging it to derby.log
Posted by Kathey Marsden <km...@sbcglobal.net>.
Bryan Pendleton wrote:
>> Kathey Marsden commented on DERBY-569:
>> --------------------------------------
>>
>> I am borderline about whether this one is appropriate for the 10.1
>> branch since it changes the behaviour of derby.drda.logConnections.
>> It might be a surprising change in a maintenance release.
>
>
> This is a good point, and I had a similar concern.
>
> How do we go about making the decision?
Well, I think if you think it adds a lot more value than confusion then
I would say go ahead and I wouldn't veto it, but I think I would insist
that it be documented in the release notes which would mean that we
would have to go from the Jira generated release notes:
http://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12310616&styleName=Html&projectId=10594&Create=Create
to some modified version. I don't know how Andrew feels about that.
The fact that we would have to do this, I think is an indicator that it
is better to wait for 10.2 for this one IMHO.
Kathey
Well thinking about it a bit I'd say let's not:
Re: [jira] Commented: (DERBY-569) Derby network server is printing
connection activity on System.out instead of logging it to derby.log
Posted by Bryan Pendleton <bp...@amberpoint.com>.
> Kathey Marsden commented on DERBY-569:
> --------------------------------------
>
> I am borderline about whether this one is appropriate for the 10.1 branch since it changes the behaviour of derby.drda.logConnections. It might be a surprising change in a maintenance release.
This is a good point, and I had a similar concern.
How do we go about making the decision?
thanks,
bryan
[jira] Commented: (DERBY-569) Derby network server is printing
connection activity on System.out instead of logging it to derby.log
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-569?page=comments#action_12377245 ]
Kathey Marsden commented on DERBY-569:
--------------------------------------
I am borderline about whether this one is appropriate for the 10.1 branch since it changes the behaviour of derby.drda.logConnections. It might be a surprising change in a maintenance release.
> 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
[jira] Resolved: (DERBY-569) Derby network server is printing connection activity on System.out instead of logging it to derby.log
Posted by "Andrew McIntyre (JIRA)" <de...@db.apache.org>.
[ 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
[jira] Commented: (DERBY-569) Derby network server is printing connection activity on System.out instead of logging it to derby.log
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ 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
[jira] Commented: (DERBY-569) Derby network server is printing connection activity on System.out instead of logging it to derby.log
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-569?page=comments#action_12357193 ]
Kathey Marsden commented on DERBY-569:
--------------------------------------
Date: Wed Nov 9 20:42:01 2005
New Revision: 332222
URL: http://svn.apache.org/viewcvs?rev=332222&view=rev
> 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
[jira] Updated: (DERBY-569) Derby network server is printing connection activity on System.out instead of logging it to derby.log
Posted by "Bryan Pendleton (JIRA)" <de...@db.apache.org>.
[ 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
[jira] Commented: (DERBY-569) Derby network server is printing connection activity on System.out instead of logging it to derby.log
Posted by "Bryan Pendleton (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-569?page=comments#action_12356989 ]
Bryan Pendleton commented on DERBY-569:
---------------------------------------
Hi Kathey,
Yes, I did run with the db2jcc driver, once I resolved my problem with having a bad copy of the driver in JAVA_HOME/jre/lib/ext.
So I was able to verify the diffs to the NSinSameJVM test in both the DerbyNet and DerbyNetClient suites.
I will mail my ICLA today; it's been sitting on my desk for a week now :)
I would be glad to update the doc as well as to udpate the release notes; are these objects under svn control in the same way as the source code? I poked around a bit inside of my 'trunk' directory, looking for the source to the docs, but didn't see anything obvious.
> 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
[jira] Reopened: (DERBY-569) Derby network server is printing
connection activity on System.out instead of logging it to derby.log
Posted by "Bryan Pendleton (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-569?page=all ]
Bryan Pendleton reopened DERBY-569:
-----------------------------------
Reopened this issue in order to merge the fix to the 10.1 branch.
> 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
[jira] Commented: (DERBY-569) Derby network server is printing connection activity on System.out instead of logging it to derby.log
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-569?page=comments#action_12356995 ]
Kathey Marsden commented on DERBY-569:
--------------------------------------
OK I will check in as soon as ...
1) I hear from you that the ICLA is in the mail
2) We have one more binding +1 for the change.
3) The vote has been up for 24 hours to allow anyone to object. 11/8/2005 1:30pm PST . (Normally I would let it sit for a week but this doesn't seem very controversial.)
Thank you for following through so completely on this change and making the doc changes. For the release notes I guess the correct thing to do for now is put this in the CHANGES file. I noticed that the CHANGES file in the trunk has not been restarted for 10.2. It would be ok to just start over with "Changes in Derby 10.2" and put your change in that text file. The release page happen at the time of the release and this note in the CHANGES file will get picked up then I think.
> 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