Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <21600284.553941279911891216.JavaMail.jira@thor>
Date: Fri, 23 Jul 2010 15:04:51 -0400 (EDT)
From: "Mamta A. Satoor (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-4601) Shutting down just a single database
 should log a different message than shutting down the system
In-Reply-To: <468721431.511081269617667240.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/DERBY-4601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12891738#action_12891738 ] 

Mamta A. Satoor commented on DERBY-4601:
----------------------------------------

By mistake, I was printing the timestamp twice in derby.log for engine shutdown. Fixed that with revision 967201.

Also, created a jira for doc updates DERBY-4755

> Shutting down just a single database should log a different message than shutting down the system
> -------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-4601
>                 URL: https://issues.apache.org/jira/browse/DERBY-4601
>             Project: Derby
>          Issue Type: Bug
>          Components: Services
>    Affects Versions: 10.5.3.0
>            Reporter: Kathey Marsden
>            Assignee: Mamta A. Satoor
>            Priority: Minor
>             Fix For: 10.7.0.0
>
>         Attachments: derby-4601.diff, DERBY4601_patch1_diff.txt, DERBY4601_patch2_diff.txt, DERBY4601_stat1_diff.txt, DERBY4601_stat2_diff.txt
>
>
> When shutting down just a single database and not the Derby system, the log should print a message that just that database was shutdown as I believe Derby is still loaded.
> e.g.
> ij version 10.6
> ij> run 'testMessages.sql';
> ij> connect 'jdbc:derby:wombat';
> ij> connect 'jdbc:derby:wombat2';
> ij(CONNECTION1)> connect 'jdbc:derby:wombat2;shutdown=true';
> ERROR 08006: Database 'wombat2' shutdown.
> ij(CONNECTION1)> connect 'jdbc:derby:;shutdown=true';
> ERROR XJ015: Derby system shutdown.
> yields the following log:
> 2010-03-26 15:27:16.375 GMT:
>  Booting Derby version The Apache Software Foundation - Apache Derby - 10.6.0.0 alpha - (927879M): instance a816c00e-0127-9b15-988d-0000002083e0 
> on database directory C:\kmarsden\repro\DERBY-4588\wombat   with class loader sun.misc.Launcher$AppClassLoader@42c042c0
> Database Class Loader started - derby.database.classpath=''
> ----------------------------------------------------------------
> 2010-03-26 15:27:16.921 GMT:
>  Booting Derby version The Apache Software Foundation - Apache Derby - 10.6.0.0 alpha - (927879M): instance 601a400f-0127-9b15-988d-0000002083e0 
> on database directory C:\kmarsden\repro\DERBY-4588\wombat2   with class loader sun.misc.Launcher$AppClassLoader@42c042c0
> Database Class Loader started - derby.database.classpath=''
> 2010-03-26 15:27:17.171 GMT:
> Shutting down instance 601a400f-0127-9b15-988d-0000002083e0 with class loader sun.misc.Launcher$AppClassLoader@42c042c0 
> ----------------------------------------------------------------
> 2010-03-26 15:27:17.218 GMT:
> Shutting down instance a816c00e-0127-9b15-988d-0000002083e0 with class loader sun.misc.Launcher$AppClassLoader@42c042c0 
> ----------------------------------------------------------------
> The first shutdown should say that just the database wombat2 was shutdown, not the entire system.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.