[ 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
