Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <427362588.1139977570236.JavaMail.jira@ajax.apache.org>
Date: Wed, 15 Feb 2006 05:26:10 +0100 (CET)
From: "Deepa Remesh (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-515) Network Server should log server start
 and shutdown time to derby.log
In-Reply-To: <521880234.1124372934257.JavaMail.jira@ajax.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/DERBY-515?page=all ]

Deepa Remesh updated DERBY-515:
-------------------------------

    Attachment: derby-515-v2.diff
                derby-515-v2.status

Attaching a revised patch 'derby-515-v2.diff' which adds timestamp to network server start and shutdown messages. 

Summary of patch:
* Changes network server start and shutdown messages to include product name, version and timestamp. I changed the messages to what Kathey suggested. With the patch, messages will look like this:
Apache Derby Network Server - 10.2.0.0 alpha started and ready to accept connections on port 1527 at  2006-02-15 03:42:51.676 GMT
Apache Derby Network Server - 10.2.0.0 alpha shutdown at 2006-02-15 03:49:14.988 GMT

* Changes only English messages. The first parameter for start message is kept the same.

* Modifies NetworkServerControlImpl to pass in the additional parameters to the messages. Formatiing of timestamp is done same way as it is done for Derby boot message.

* Modifies master files.

* Since the changed master files contain version information, they are added to tools\release\build.xml so that version will get bumped at release time.

In Derby Server and Admin guide, we may have to change the messages in sample output for NsSample program. I will open another  jira once this patch is reviewed and committed.

I have a couple of questions and would appreciate if someone can answer them:
1. I found that the test derbynet/NSinSameJVM.java has two masters - one for client and one for jcc driver. These masters are identical. Can we remove these and keep a single copy in top "master" folder? 
2. Will it be useful to add timestamp to messages for other netwrok server commands (like trace, timeslice, maxthreads etc) ?

With this patch, I ran derbynetmats and derbynetclientmats with Sun JDK 1.4.2 on Win XP. No failures. 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-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