[ 
https://issues.apache.org/jira/browse/DERBY-5051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13003958#comment-13003958
 ] 

Kim Haase commented on DERBY-5051:
----------------------------------

Oh, I see. the setting(s) of the property or properties shows up in the 
redirected log? I guess I didn't quite grasp that. Wouldn't you have to know 
where the log info was going already in order to even find the log with these 
settings in it? I suppose it might be helpful if you needed to send the log 
contents somewhere for diagnostic purposes.

Anyway, I'll reopen this issue and put a mention in each of the Reference 
Manual entries as well as in the error log topic in the developer's guide.

> 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

Reply via email to