Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Wed, 9 Mar 2011 23:54:59 +0000 (UTC)
From: "Kathey Marsden (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <1458842435.9581.1299714899633.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1197335317.1144.1298009952376.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] Commented: (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:comment-tabpanel&focusedCommentId=13004881#comment-13004881 ] 

Kathey Marsden commented on DERBY-5051:
---------------------------------------

It would be nice to have a specific test case or tool that runs and generates the doc derby.log examples. I think we have something like that for the SQLStates that can change frequently.   I think for that one it is part of the release process, which I know we don't want to grow, but just reducing the log update task to a quick cut and paste would be an improvement.


> 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-2.diff, DERBY-5051-2.stat, DERBY-5051-2.zip, 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