[ http://issues.apache.org/jira/browse/DERBY-515?page=comments#action_12366519 ]
Bryan Pendleton commented on DERBY-515: --------------------------------------- I think this is quite nice -- thanks! I don't see any need to timestamp the trace or other messages at this time. I think we should just start with the startup and shutdown messages and get some feel for it. Why did you choose GMT for the timestamp? Since it's intended for a human to read, it seems like it might be slightly nicer to display the time in the server's local timezone? Lastly, what do you think about handling the version number in the error message with a test-time filter, the same way that the xxxxxxFILTERED-TIMESTAMPxxxxxx is handled, so that the master test files would say xxxxxxFILTERED-VERSION-NUMBERxxxxxx? Presumably, we could make it so that the software which did the filtering verified that the version number was correct, then filtered it out; that would mean fewer files had to change when bumping the version number. > Network Server should log server start and shutdown time to derby.log > --------------------------------------------------------------------- > > Key: DERBY-515 > URL: http://issues.apache.org/jira/browse/DERBY-515 > Project: Derby > Type: Improvement > Components: Network Server > Versions: 10.1.2.0, 10.2.0.0 > Reporter: Kathey Marsden > Assignee: Deepa Remesh > Fix For: 10.2.0.0 > Attachments: derby-515-v2.diff, derby-515-v2.status > > Network server currently only reports the start and stop of network server to > the console output and does not print an associated timestamp. > It would be helpful if the start and stop times of network server were > recorded in the derby.log, so there would not be a need to check t the > console output. -- 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
