[
https://issues.apache.org/jira/browse/DERBY-2182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550670
]
Kim Haase commented on DERBY-2182:
----------------------------------
I tried using the embedded driver and got no autobooting even if I set
derby.system.home explicitly in the derby.properties file, as far as I could
tell.
jdench 50 =>java -jar $DERBY_HOME/lib/derbyrun.jar ij
ij version 10.3
ij> show connections;
No connections available.
ij> exit;
jdench 51 =>
And derby.log is empty.
But I would have expected that, since it was my understanding that autobooting
only applied to the Network Server.
And the really weird thing is that if I then start the Network Server again,
*with* derby.system.home set in my derby.properties file, the databases *don't*
autoboot! Exactly the opposite behavior from yours! When I remove the
derby.system.home setting, they autoboot the same as before.
Very strange.
> 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.
