[ 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
