db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (DERBY-4853) log derby.properties location and derby.log location to derby.log
Date Sun, 20 Mar 2011 00:28:29 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kathey Marsden resolved DERBY-4853.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 10.7.1.3
                   10.6.2.3
                   10.5.3.2

Finished backporting to 10.5.  For 10.5 there was a comment error so it does not show on the
subversion commits the 10.5 change was revision 1083351


> 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: Improvement
>          Components: Services
>    Affects Versions: 10.5.3.0
>            Reporter: Kathey Marsden
>            Assignee: Mamta A. Satoor
>              Labels: derby_triage10_8
>             Fix For: 10.5.3.2, 10.6.2.3, 10.7.1.3, 10.8.0.0
>
>         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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message