[
https://issues.apache.org/jira/browse/DERBY-4853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamta A. Satoor updated DERBY-4853:
-----------------------------------
Attachment: DERBY4853_patch1_diff.txt
It will be useful to know in derby.log, the possible locations of
derby.properties and derby.log. Following 2 additional properties will now
always be put in derby.log (every time a database is booted. Similar to
existing jvminfo that is printed in derby.log)
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.
Hopefully this additional information in the log file will be handy when
working with customer issues. I have attached the patch for the code changes to
accomplish above logging enhancement.
> log derby.properties location and derby.log location to derby.log
> -----------------------------------------------------------------
>
> Key: DERBY-4853
> URL: https://issues.apache.org/jira/browse/DERBY-4853
> Project: Derby
> Issue Type: Bug
> Components: Services
> Affects Versions: 10.5.3.0
> Reporter: Kathey Marsden
> Assignee: Mamta A. Satoor
> Attachments: DERBY4853_patch1_diff.txt
>
>
> Often when a Derby issue occurs, the derby.log is the one thing that does get
> retrieved, but often gets passed through many layers before it reaches the
> people supporting Derby. It would be helpful if derby.log also included the
> following to help instruct customers how to change derby.properties or look
> again at the log.
> 1) derby.properties location.
> 2) derby.log location or indicate how error log redirection is defined.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
