[
http://issues.apache.org/jira/browse/DERBY-515?page=comments#action_12367233 ]
Deepa Remesh commented on DERBY-515:
------------------------------------
Suresh pointed out to me that this change caused the following failure in
derbynetclientmats with 10.1 client and 10.2 server:
derbynetclientmats/derbynetmats/derbynetmats.fail:derbynet/testProperties.java:
(< Shutdown successful.
6a6
> Apache Derby Network Server - 10.2.0.0 alpha shutdown at
xxxxxxFILTERED-TIMESTAMPxxxxxGMT
11 del
)
The diff is in the shutdown message. The test executes a process to shutdown
the network server that it started. This process currently dumps results to
standard out. I am planning to change this test to make the shutdown process
not write to the standard output. The test can use execCmd instead of
execCmdDumpResults method for the shutdown process. I will submit a patch for
this in a while.
> 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
