[ http://issues.apache.org/jira/browse/DERBY-515?page=all ]
Deepa Remesh updated DERBY-515:
-------------------------------
Attachment: derby-515-patch2-v1.diff
derby-515-patch2-v1.status
Attaching a second patch 'derby-515-patch2-v1.diff' for Kathey's comments.
Summary of patch:
* Removes identical master files in DerbyNetClient and DerbyNet for
derbynet/NSinSameJVM.java and moves it the top master directory.
* Modified tools/release/build.xml to point to the new master file.
* Adds comments as to why CheapDateFormatter and GMT is used to format
timestamp. Moves formatting of timestamp to a method getFormattedTimestamp().
This will be helpful if timestamp is planned to be used for more messages as
Kathey indicated. I will open a JIRA for this.
With this patch, I ran derbynetmats and derbynetclientmats with Sun JDK1.4.2. 1
failure in derbynetmats (jdbcapi/checkDataSource30.java) also seen in tinderbox
tests. Please take a look at this patch. Thanks.
> 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-patch2-v1.diff, derby-515-patch2-v1.status,
> 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
