[jira] [Resolved] (UIMA-4688) DUCC should self-detect and provide an alert when unable to write its log files

["Richard Eckart de Castilho (Jira)" <de...@uima.apache.org>]

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

Richard Eckart de Castilho resolved UIMA-4688.
----------------------------------------------
    Resolution: Abandoned

DUCC has been retired.

> DUCC should self-detect and provide an alert when unable to write its log files
> -------------------------------------------------------------------------------
>
>                 Key: UIMA-4688
>                 URL: https://issues.apache.org/jira/browse/UIMA-4688
>             Project: UIMA
>          Issue Type: New Feature
>          Components: DUCC
>            Reporter: Lou DeGenaro
>            Priority: Major
>             Fix For: future-DUCC
>
>
> In the case where DUCC's log files are written to a filesystem with a quota, when the quota is exceeded DUCC will be prevented from writing its logs.  Usually the inability to write to the file system would result in an Exception with reason "quota exceeded".  However, log4j v1 suppresses exceptions and continues as if all is well.
> Some possible alternatives:
> 1. use log4j v2
> 2. use native Java logging
> 3. use an alternative filesystem not writeable detection mechanism



--
This message was sent by Atlassian Jira
(v8.20.10#820010)