Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Fri, 4 Mar 2011 22:18:46 +0000 (UTC)
From: "Kim Haase (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <1599268562.224.1299277126083.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1197335317.1144.1298009952376.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] Resolved: (DERBY-5051) Update the docs to include the
 additional information available in derby.log. This information will be
 useful from product supportability stand point
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DERBY-5051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kim Haase resolved DERBY-5051.
------------------------------

          Resolution: Fixed
       Fix Version/s: 10.8.0.0
    Issue & fix info:   (was: [Patch Available])

Thanks, Rick. I've committed this patch so it can get into the 10.8 RC. If any changes are needed, I can still make them on the trunk and if a second RC is needed, they can get into the release.

Committed patch DERBY-5051.diff to documentation trunk at revision 1078171. 

> Update the docs to include the additional information available in derby.log. This information will be useful from product supportability stand point
> -----------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-5051
>                 URL: https://issues.apache.org/jira/browse/DERBY-5051
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions: 10.8.0.0
>            Reporter: Mamta A. Satoor
>            Assignee: Kim Haase
>             Fix For: 10.8.0.0
>
>         Attachments: DERBY-5051.diff, DERBY-5051.stat, DERBY-5051.zip
>
>
> With DERBY-4853, we log additional information in derby.log to make it easier for the support group to work with customer problems.
> Following 2 additional properties will now always be put in derby.log (every time a database is booted) 
> user.dir 
> derby.system.home 
> user.dir is the system property which gives the user working directory. 
> If the user has not specified derby,system.home, then Derby will look for optional derby.properties file in user.dir . If user has provided derby.system.home, then the optional derby.properties will be looked in derby.system.home rather than user.dir 
> If user has not provided derby.system.home, then a sample of the 2 properties on derby.log looks as follows on my machine 
> user.dir=C:\p4clients\svnmain\client2\trunk\systest\out142 
> derby.system.home=null 
> If user has set derby.system.home to c:./temp, then a sample of the 2 properties on derby.log looks as follows on my machine 
> user.dir=C:\p4clients\svnmain\client2\trunk\systest\out142 
> derby.system.home=c:/temp 
> In addition to the above 2 properties, there can be following 3 optional properties in the log (following the 2 properties mentioned above) 
> derby.stream.error.file 
> derby.stream.error.method 
> derby.stream.error.field 
> The above 3 properties provide a way to alter where error messages get logged rather than tranditional derby.log file. In the absence of the above 3 optional properties, the location of derby.log follows the same logic as derby.properties. But if the user has set any or all of the 3 optional properties, then derby.log will not be in same location as derby.properties. In the Derby code, derby.stream.error.file takes precedence over the other 2 properties and derby.stream.error.method take precedence over the last property. 

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira