[
https://issues.apache.org/jira/browse/DERBY-5051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim Haase updated DERBY-5051:
-----------------------------
Attachment: DERBY-5051.zip
DERBY-5051.stat
DERBY-5051.diff
Attaching DERBY-5051.diff, DERBY-5051.stat, and DERBY-5051.zip, containing
edits to the following files. Not all the edits are strictly log-related -- I
hope that is all right? Explanations below.
M src/tools/rtoolssysinfo1002629.dita
M src/devguide/cdevdvlp27715.dita
M src/devguide/tdevdvlp20349.dita
M src/devguide/cdevdvlp25889.dita
M src/getstart/tgssetupverify.dita
M src/getstart/twwdactivity1.dita
M src/getstart/twwdactivity3_Setup.dita
M src/getstart/twwdactivity2.dita
M src/getstart/twwdactivity4.dita
I updated the contents of the derby.log output in cdevdvlp27715.dita (Booting
databases), tdevdvlp20349.dita (Shutting down the system), and
twwdactivity1.dita (Creating a Derby database and running SQL statements). I
did not include the istat messages at the end of the shutdown log entry, since
those are disappearing, for the time being at least.
I added information about the log to cdevdvlp27715.dita and updated the
information in cdevdvlp25889.dita (The error log). I hope this is correct.
I hope it is okay that I added a few more things:
I took the opportunity to add information about the deregister attribute to the
shutdown topic (tdevdvlp20349.dita), since it seemed to belong there, and I had
missed this topic in the patch for DERBY-5043.
I also took the opportunity to make some updates that are not strictly
log-related but that have to be made for every release -- fixing the output for
examples in the Getting Started and Tools guides. These do not use the final
release number and build because that isn't available yet.
> 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
> 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
