db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@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
Date Wed, 02 Mar 2011 18:28:36 GMT

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

Knut Anders Hatlen commented on DERBY-5051:
-------------------------------------------

I added a release note to DERBY-4939 that mentions the properties derby.storage.indexStats.auto
and derby.storage.indexStats.log, so even if we don't get around to documenting them, at least
there's some info available about them to those who download the release.

But given that the logging is primarily meant for debugging, and the messages may confuse
users and possibly make them believe there is a problem, I'm leaning towards disabling the
istat logging by default. If users have problems that we suspect may have something to do
with istat, we can always ask them to enable extra logging manually.

> 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
>
> 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

        

Mime
View raw message