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 "Thorsten Möller (JIRA)" <de...@db.apache.org> on 2006/03/08 09:59:03 UTC
[jira] Created: (DERBY-1086) Location of derby.properties file
Location of derby.properties file
---------------------------------
Key: DERBY-1086
URL: http://issues.apache.org/jira/browse/DERBY-1086
Project: Derby
Type: Improvement
Components: Unknown
Environment: all
Reporter: Thorsten Möller
Priority: Minor
As with (at least) version 10.1.2.1 the configuration file "derby.properties" must be located in the directory where all databases will be stored. It should be possible to have this file anywhere in the filesystem for flexibility. Most projects which use Derby as one component use a central directory where all configuration files reside.
Then, for startup of Derby there has to be a property which tells Derby where to find the properties file, for example "derby.properties.file.path". If that property is not set on startup the system might fall back to the current behaviour, i.e. try to find the properties file in its database directory.
--
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
[jira] Commented: (DERBY-1086) Location of derby.properties file
Posted by "John H. Embretsen (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1086?page=comments#action_12370187 ]
John H. Embretsen commented on DERBY-1086:
------------------------------------------
Thorsten,
In that case, I would say you have found a bug. However, I was not able to reproduce it. Below is a description of what I did:
I created a test directory, "derby-prop", with subdirectories "databases", "logs" and "home".
In the "derby-prop/home" directory, I created a derby.properties file with the following property:
derby.stream.error.file=../logs/derby.log
Notice that I specified the log directory relative to the directory that I intend to specify as derby.system.home. It is also possible to specify an absolute path.
I started IJ from the "derby-prop" directory, but with derby.system.home set to the "home" subdirectory:
java -Dderby.system.home=./home org.apache.derby.tools.ij
In IJ, I created a database called "testDB" in the "derby-prop/databases" directory:
connect 'jdbc:derby:../databases/testDB;create=true';
Notice that the url is relative to derby.system.home, which I set to "derby-prop/home".
I then shut down the database and exited IJ.
I found derby.log in the directory derby-prop/logs, which is what is specified by the derby.stream.error.file property.
There was no log file in the directory specified by derby.system.home, meaning that the derby.stream.error.file property was _not_ ignored.
What are you doing differently to make derby ignore this property?
(Note: I tried this with the current 10.2 development trunk, but I will be surprised if 10.1.2.1 behaves differently in this case).
> Location of derby.properties file
> ---------------------------------
>
> Key: DERBY-1086
> URL: http://issues.apache.org/jira/browse/DERBY-1086
> Project: Derby
> Type: Improvement
> Components: Unknown
> Environment: all
> Reporter: Thorsten Möller
> Priority: Minor
>
> As with (at least) version 10.1.2.1 the configuration file "derby.properties" must be located in the directory where all databases will be stored. It should be possible to have this file anywhere in the filesystem for flexibility. Most projects which use Derby as one component use a central directory where all configuration files reside.
> Then, for startup of Derby there has to be a property which tells Derby where to find the properties file, for example "derby.properties.file.path". If that property is not set on startup the system might fall back to the current behaviour, i.e. try to find the properties file in its database directory.
--
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
[jira] Commented: (DERBY-1086) Location of derby.properties file
Posted by "Thorsten Möller (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1086?page=comments#action_12370180 ]
Thorsten Möller commented on DERBY-1086:
----------------------------------------
I tried what is recommended by this thread but it doesn't work well. In particular, setting the property derby.system.home to the dir where the derby.properties file is located and point to another dir in the JDBC connect URL shows the effect that the log file is created in the dir referenced by derby.system.home even if the property derby.stream.error.file is set in derby.properties. It seems that this property is ignored in this case.
> Location of derby.properties file
> ---------------------------------
>
> Key: DERBY-1086
> URL: http://issues.apache.org/jira/browse/DERBY-1086
> Project: Derby
> Type: Improvement
> Components: Unknown
> Environment: all
> Reporter: Thorsten Möller
> Priority: Minor
>
> As with (at least) version 10.1.2.1 the configuration file "derby.properties" must be located in the directory where all databases will be stored. It should be possible to have this file anywhere in the filesystem for flexibility. Most projects which use Derby as one component use a central directory where all configuration files reside.
> Then, for startup of Derby there has to be a property which tells Derby where to find the properties file, for example "derby.properties.file.path". If that property is not set on startup the system might fall back to the current behaviour, i.e. try to find the properties file in its database directory.
--
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
[jira] Commented: (DERBY-1086) Location of derby.properties file
Posted by "Thorsten M?ller (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1086?page=comments#action_12370669 ]
Thorsten Möller commented on DERBY-1086:
----------------------------------------
John,
I don't know what went wrong on my fist test. I re-checked everything and now it works as expected. This issue can be closed.
Thanks for your help.
> Location of derby.properties file
> ---------------------------------
>
> Key: DERBY-1086
> URL: http://issues.apache.org/jira/browse/DERBY-1086
> Project: Derby
> Type: Improvement
> Components: Unknown
> Environment: all
> Reporter: Thorsten Möller
> Priority: Minor
>
> As with (at least) version 10.1.2.1 the configuration file "derby.properties" must be located in the directory where all databases will be stored. It should be possible to have this file anywhere in the filesystem for flexibility. Most projects which use Derby as one component use a central directory where all configuration files reside.
> Then, for startup of Derby there has to be a property which tells Derby where to find the properties file, for example "derby.properties.file.path". If that property is not set on startup the system might fall back to the current behaviour, i.e. try to find the properties file in its database directory.
--
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
[jira] Commented: (DERBY-1086) Location of derby.properties file
Posted by "John H. Embretsen (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1086?page=comments#action_12369428 ]
John H. Embretsen commented on DERBY-1086:
------------------------------------------
Please read the following thread from the derby-user mailing list and see if that solves your problem:
http://www.nabble.com/Specifying-the-Derby-Database-Location-t1038003.html
In short, databases do not currently have to be stored in the same directory as the derby.properties file, since you can specify database URLs relative to derby.system.home.
> Location of derby.properties file
> ---------------------------------
>
> Key: DERBY-1086
> URL: http://issues.apache.org/jira/browse/DERBY-1086
> Project: Derby
> Type: Improvement
> Components: Unknown
> Environment: all
> Reporter: Thorsten Möller
> Priority: Minor
>
> As with (at least) version 10.1.2.1 the configuration file "derby.properties" must be located in the directory where all databases will be stored. It should be possible to have this file anywhere in the filesystem for flexibility. Most projects which use Derby as one component use a central directory where all configuration files reside.
> Then, for startup of Derby there has to be a property which tells Derby where to find the properties file, for example "derby.properties.file.path". If that property is not set on startup the system might fall back to the current behaviour, i.e. try to find the properties file in its database directory.
--
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
[jira] Closed: (DERBY-1086) Location of derby.properties file
Posted by "Andrew McIntyre (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1086?page=all ]
Andrew McIntyre closed DERBY-1086:
----------------------------------
Fix Version: 10.2.0.0
Resolution: Cannot Reproduce
Closing at reporter's request.
> Location of derby.properties file
> ---------------------------------
>
> Key: DERBY-1086
> URL: http://issues.apache.org/jira/browse/DERBY-1086
> Project: Derby
> Type: Improvement
> Components: Unknown
> Environment: all
> Reporter: Thorsten Möller
> Priority: Minor
> Fix For: 10.2.0.0
>
> As with (at least) version 10.1.2.1 the configuration file "derby.properties" must be located in the directory where all databases will be stored. It should be possible to have this file anywhere in the filesystem for flexibility. Most projects which use Derby as one component use a central directory where all configuration files reside.
> Then, for startup of Derby there has to be a property which tells Derby where to find the properties file, for example "derby.properties.file.path". If that property is not set on startup the system might fall back to the current behaviour, i.e. try to find the properties file in its database directory.
--
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