[ 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
