[ http://issues.apache.org/jira/browse/DERBY-515?page=all ]
Deepa Remesh updated DERBY-515:
-------------------------------
Attachment: derby-515.diff
derby-515.status
Attaching a patch 'derby-515.diff' which does the following:
* Adds timestamp to server start and shutdown messages written to derby.log and
console. Timestamp formatting is done in the same way as it is done for Derby
boot message.
* Adds additional parameters to start and shutdown messages in the properties
files.
* Modifies test output of derbynet/NSinSameJVM.java and
derbynet/testProperties.java
Ran derbyall with Sun JDK 1.4.2 on Windows XP. No failures. Please
review/commit this patch. Thanks.
For the issue mentioned by Oystein "This would be even more helpful if the
derby.log file was not overwritten on the next startup. (Probably a separate
issue)." - property derby.infolog.append can be used to avoid overwriting
derby.log file.
> 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.diff, derby-515.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
