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 2013/10/24 23:58:05 UTC

[jira] [Closed] (UIMA-3373) DUCC logging - should set -Dlog4j.configuration when spawning DUCC processes

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

Burn Lewis closed UIMA-3373.
----------------------------


Ironically this change was probably only necessary for the JD as the rest of the daemons have a clean classpath.

> DUCC logging - should set -Dlog4j.configuration when spawning DUCC processes
> ----------------------------------------------------------------------------
>
>                 Key: UIMA-3373
>                 URL: https://issues.apache.org/jira/browse/UIMA-3373
>             Project: UIMA
>          Issue Type: Improvement
>          Components: DUCC
>    Affects Versions: 1.0-Ducc
>            Reporter: Jim Challenger
>            Assignee: Burn Lewis
>            Priority: Minor
>             Fix For: 1.0-Ducc
>
>
> -Dlog4j.configurationFile='path_to_log4j.xml'
> The log4j correct config must be enforced to avoid extraneous configs in the classpath from interfering with DUCC's logging.
> I'll do the scripting that spawns the DUCC daemons and pass to Lou/Burn to do the Orchestrator / CLI part.



--
This message was sent by Atlassian JIRA
(v6.1#6144)