[ 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
