db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta A. Satoor (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (DERBY-4853) log derby.properties location and derby.log location to derby.log
Date Sat, 16 Oct 2010 01:38:33 GMT

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

Mamta A. Satoor reassigned DERBY-4853:
--------------------------------------

    Assignee: Mamta A. Satoor

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


Mime
View raw message