db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta A. Satoor (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4601) Shutting down just a single database should log a different message than shutting down the system
Date Tue, 20 Jul 2010 17:30:50 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mamta A. Satoor updated DERBY-4601:
-----------------------------------

    Attachment: DERBY4601_patch2_diff.txt
                DERBY4601_stat2_diff.txt

Thanks, Knut, for taking the time to review the patch. In loc/messages.xml, I have removed
the blank space after the message. The colon is needed to separate the message from the timestamp
header. I have changed BaseMonitor.java to take care of that colon rather than putting it
directly in messages.xml. In BaseDataFileFactory.java, I have removed the english text and
added it to the existing message in messages.xml.

Please let me know if you have any further comments.

> 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
>         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.


Mime
View raw message