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 2016/07/07 19:45:11 UTC

[jira] [Closed] (UIMA-5003) The internal broker used by DD jobs creates many log4j exceptions

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

Burn Lewis closed UIMA-5003.
----------------------------
    Resolution: Fixed

Hide logging-related properties when starting broker.
Make UimaAsProcessContainer use the class-loading code in DuccJobService rather than duplicating the code ... also share its hide/restore-logging-properties methods.

> The internal broker used by DD jobs creates many log4j exceptions 
> ------------------------------------------------------------------
>
>                 Key: UIMA-5003
>                 URL: https://issues.apache.org/jira/browse/UIMA-5003
>             Project: UIMA
>          Issue Type: Bug
>          Components: DUCC
>            Reporter: Burn Lewis
>            Assignee: Burn Lewis
>            Priority: Minor
>             Fix For: 2.1.0-Ducc
>
>
> The JP launches the internal broker with an AMQ-only classpath but the user's log4j configuration file may reference classes that are only on the user's classpath ... and so will fail to create many of the loggers and generate many errors.



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