You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kim Haase (JIRA)" <ji...@apache.org> on 2011/02/28 21:22:36 UTC
[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
[ https://issues.apache.org/jira/browse/DERBY-5051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13000500#comment-13000500 ]
Kim Haase commented on DERBY-5051:
----------------------------------
I'll get to work on this, but I have a question. I looked at the new output after building derby from the code trunk.
At least at present it seems that in addition to reporting the user.dir and derby.system.home settings, the log also contains the following at the end, after the "Shutting down ..." message:
Mon Feb 28 14:47:23 EST 2011 Thread[main,5,main] {istat} stopping daemon, active=false, work/age=0/47446 [q/p/s=0/0/0,err:k/u/c=0/0/0,rej:f/d/o=0/0/0]
What's this? Will it appear in the output of the released version?
> 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