db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "A.S.Thiwanka Somasiri (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4601) Shutting down just a single database should log a different message than shutting down the system
Date Mon, 12 Apr 2010 03:53:41 GMT

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

A.S.Thiwanka Somasiri commented on DERBY-4601:
----------------------------------------------

Hi all,
            I think this is not a case of Derby system shutdown. It simply logs non-descriptive
messages to separately identify the database shutdown and system shutdown in derby.log.

CONNECT 'jdbc:derby:firstdb;create=true';

This command creates a database if not existing one with name firstdb, with which the JDBC
protocol specification for the Derby driver "jdbc:derby".
So even if the Derby system is down it starts the Derby engine and create the database.

So even we issue the command CONNECT 'jdbc:derby:firstdb;shutdown=true'; and then issue the
CONNECT 'jdbc:derby:firstdb;create=true';
the system shutdown first and then get started.So, as I understood there is not a problem
with the Derby system shutdown.It is just a case of logging in the derby.log file.

If there is any misunderstanding, please correct it...!

Thank you all.


> 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
>            Priority: Minor
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message