You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Burn Lewis (JIRA)" <de...@uima.apache.org> on 2015/03/19 19:31:38 UTC

[jira] [Reopened] (UIMA-4253) DUCC's JP should manage user provided log4j configuration

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

Burn Lewis reopened UIMA-4253:
------------------------------
      Assignee: Burn Lewis  (was: Jerry Cwiklik)

Found other logging properties that DUCC should ignore

> DUCC's JP should manage user provided log4j configuration
> ---------------------------------------------------------
>
>                 Key: UIMA-4253
>                 URL: https://issues.apache.org/jira/browse/UIMA-4253
>             Project: UIMA
>          Issue Type: Bug
>          Components: DUCC
>            Reporter: Jerry Cwiklik
>            Assignee: Burn Lewis
>             Fix For: 2.0.0-Ducc
>
>
> User log4j configuration provided via -Dlog4j.configuration should not be available to Ducc container which is running in a dedicated Classloader separate from a user container. If the -D is provided, the code should save the configuration file and remove the property from System.properties before executing Ducc code. The code should restore log4j.configuration property before crossing ducc/user boundary while deploying and initializing analytics.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)