[
https://issues.apache.org/jira/browse/DERBY-4601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12857233#action_12857233
]
Eranda Sooriyabandara commented on DERBY-4601:
----------------------------------------------
Hi Kathey,
Here I found out something.
The log message is all about shutting down single database not the full system.
When we shutdown full system it logs which database shuts. It don't print as as
a system shut.
Here I connect some database instances
----------------------------------------------------------------
2010-04-15 07:55:56.686 GMT:
Booting Derby version The Apache Software Foundation - Apache Derby - 10.6.0.0
alpha - (1): instance a816c00e-0128-0077-9584-0000009e19d8
on database directory E:\GSoC-2010\Derby-2785\trunk\wombat with class loader
sun.misc.launcher$appclassloa...@11b86e7
Database Class Loader started - derby.database.classpath=''
----------------------------------------------------------------
2010-04-15 07:56:00.828 GMT:
Booting Derby version The Apache Software Foundation - Apache Derby - 10.6.0.0
alpha - (1): instance 601a400f-0128-0077-9584-0000009e19d8
on database directory E:\GSoC-2010\Derby-2785\trunk\wombat2 with class loader
sun.misc.launcher$appclassloa...@11b86e7
Database Class Loader started - derby.database.classpath=''
----------------------------------------------------------------
2010-04-15 07:56:03.966 GMT Thread[main,5,main] Cleanup action starting
2010-04-15 07:56:15.917 GMT:
Booting Derby version The Apache Software Foundation - Apache Derby - 10.6.0.0
alpha - (1): instance f81e0010-0128-0077-9584-0000009e19d8
on database directory E:\GSoC-2010\Derby-2785\trunk\wombat3 with class loader
sun.misc.launcher$appclassloa...@11b86e7
Database Class Loader started - derby.database.classpath=''
----------------------------------------------------------------
2010-04-15 07:56:33.415 GMT:
Booting Derby version The Apache Software Foundation - Apache Derby - 10.6.0.0
alpha - (1): instance d381409a-0128-0077-9584-0000009e19d8
on database directory E:\GSoC-2010\Derby-2785\trunk\wombat4 with class loader
sun.misc.launcher$appclassloa...@11b86e7
Database Class Loader started - derby.database.classpath=''
And shut them at once with the path with the additional part of absolute path
of the database directory. What I get in the log was
2010-04-15 07:57:09.015 GMT:
Shutting down instance E:\GSoC-2010\Derby-2785\trunk\wombat4
d381409a-0128-0077-9584-0000009e19d8 with class loader
sun.misc.launcher$appclassloa...@11b86e7
----------------------------------------------------------------
2010-04-15 07:57:09.104 GMT:
Shutting down instance E:\GSoC-2010\Derby-2785\trunk\wombat3
f81e0010-0128-0077-9584-0000009e19d8 with class loader
sun.misc.launcher$appclassloa...@11b86e7
----------------------------------------------------------------
2010-04-15 07:57:09.191 GMT:
Shutting down instance E:\GSoC-2010\Derby-2785\trunk\wombat2
601a400f-0128-0077-9584-0000009e19d8 with class loader
sun.misc.launcher$appclassloa...@11b86e7
----------------------------------------------------------------
2010-04-15 07:57:09.223 GMT:
Shutting down instance E:\GSoC-2010\Derby-2785\trunk\wombat
a816c00e-0128-0077-9584-0000009e19d8 with class loader
sun.misc.launcher$appclassloa...@11b86e7
----------------------------------------------------------------
That means though we shut all the connection at once it shuts connections one
by one and log separately.
So I think the better way is to add the database name to the log. What you
think?
> 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$appclassloa...@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$appclassloa...@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$appclassloa...@42c042c0
> ----------------------------------------------------------------
> 2010-03-26 15:27:17.218 GMT:
> Shutting down instance a816c00e-0127-9b15-988d-0000002083e0 with class loader
> sun.misc.launcher$appclassloa...@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
