You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Rajesh Kartha (JIRA)" <ji...@apache.org> on 2006/12/01 17:14:26 UTC
[jira] Updated: (DERBY-2136) Can't set system directory with
derby.system.home for Network Server
[ http://issues.apache.org/jira/browse/DERBY-2136?page=all ]
Rajesh Kartha updated DERBY-2136:
---------------------------------
If the DERBY_OPTS has been set with -Dderby.system.home correctly, the Network Server will for sure use that as the Derby system home. Did you try creating databases by connecting to the server ? I am sure you will find them in the /data/derby directory, in your case.
Currently the sysinfo utility, in both cases (embedded and NetworkServer), does not print the derby.system.home information, hence I think what you noticed is expected. However, I do agree with you it will be really useful for the sysinfo to print the derby.system.home info out, specially when there are multiple instances of server running on a machine and one wants to verify if the derby.system.home is kept separate from each other.
> Can't set system directory with derby.system.home for Network Server
> --------------------------------------------------------------------
>
> Key: DERBY-2136
> URL: http://issues.apache.org/jira/browse/DERBY-2136
> Project: Derby
> Issue Type: Bug
> Components: Documentation, Network Server
> Reporter: Frederik
> Priority: Minor
>
> I'm a total newcomer to Derby. Decided to play with it today after reading http://www.regdeveloper.co.uk/2006/11/08/java_database_derby
> I want to use the Network Server deployment mode. For determining the System Directory (which holds properties file and the database directories, etc), I understood from docs (e.g. http://db.apache.org/derby/docs/10.2/devguide/cdevdvlp27610.html) that I should set derby.system.home.
> I tried (using the newer scripts in $DERBY_HOME/bin)
> export DERBY_OPTS=-Dderby.system.home=/data/derby
> startNetworkServer
> but that failed to set the system directory properly (as witnessed by "NetworkServerControl sysinfo"). It was using current directory when starting derby.
> I finally discovered that it works if I do
> export DERBY_OPTS=-Duser.dir=/data/derby
> startNetworkServer
> That seems to be either a bug or a docbug to me.
> (Almost all docs are using the scripts in $DERBY_HOME/frameworks/NetworkServer/bin instead of the newer ones in ./bin ; except for http://db.apache.org/derby/docs/10.2/getstart/ and the mention in 10.2 release notes)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira