[
https://issues.apache.org/jira/browse/DERBY-2182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550662
]
Kim Haase commented on DERBY-2182:
----------------------------------
As best I can tell, yes, I am seeing an autoboot of the databases in the
current directory. The only line in my derby.properties file is
derby.system.bootAll=true
Unless there is some mechanism that sets derby.system.home under the covers
somewhere, it's not set as far as I know.
In a directory that has three databases, I start the Network Server:
java -jar $DERBY_HOME/lib/derbyrun.jar server start
Security manager installed using the Basic server security policy.
Apache Derby Network Server - 10.3.1.4 - (561794) started and ready to accept
connections on port 1527 at 2007-12-11 15:33:29.313 GMT
Apache Derby Network Server - 10.3.1.4 - (561794) shutdown at 2007-12-11
18:08:09.617 GMT
The following shows up in derby.log, indicating that two of the databases
autobooted:
----------------------------------------------------------------
2007-12-11 15:33:28.639 GMT:
Booting Derby version The Apache Software Foundation - Apache Derby - 10.3.1.4
- (561794): instance c013800d-0116-c9d6-d6d5-fffff516f185
on database directory /home/chaase/javadb/DERBYDBS/jdbcDemoDB
Database Class Loader started - derby.database.classpath=''
----------------------------------------------------------------
2007-12-11 15:33:29.163 GMT:
Booting Derby version The Apache Software Foundation - Apache Derby - 10.3.1.4
- (561794): instance a816c00e-0116-c9d6-d6d5-fffff516f185
on database directory /home/chaase/javadb/DERBYDBS/seconddb
Database Class Loader started - derby.database.classpath=''
Apache Derby Network Server - 10.3.1.4 - (561794) started and ready to accept
connections on port 1527 at 2007-12-11 15:33:29.313 GMT
For the other database, I previously made that
syscs_util.syscs_set_database_property call, so its service.properties file
includes the following line:
derby.database.noAutoBoot=true
So that one doesn't autoboot.
I haven't tried using the embedded driver yet.
> Documentation for derby.system.bootAll is missing
> -------------------------------------------------
>
> Key: DERBY-2182
> URL: https://issues.apache.org/jira/browse/DERBY-2182
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Reporter: Dag H. Wanvik
> Assignee: Kim Haase
> Priority: Minor
> Attachments: DERBY-2182.diff, DERBY-2182.stat, DERBY-2182.zip
>
>
> This property is not documented in the Tuning Derby guide, but it is referred
> to
> in the developer's guide in a couple of places with dangling pointers to the
> Tuning Guide:
> http://db.apache.org/derby/docs/dev/devguide/cdevdvlp27715.html
> http://db.apache.org/derby/docs/dev/devguide/cdevcsecure60146.html
> http://db.apache.org/derby/docs/dev/devguide/cdevadvjdbc41138.html
> Googling, I find it documented in older Cloudscape docs e.g. in
> http://www.novell.com/documentation/extendas37/docs/help/java/jdkee/cloudscape/doc/html/coredocs/proper42.htm#1014327,
> but not in Cloudscape 10 docs, e.g.
> http://publib.boulder.ibm.com/infocenter/cldscp10/topic/com.ibm.cloudscape.doc/perf63.htm
> which could indicate it was removed for some reason. So, either we
> should document it anew or remove the references to it. If we decide to keep
> it, we should also consider
> derby.database.noAutoBoot (not currently documented).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
