uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Burn Lewis (JIRA)" <...@uima.apache.org>
Subject [jira] [Resolved] (UIMA-5117) UIMA-AS: dd2spring should log at INFO
Date Thu, 22 Sep 2016 21:33:20 GMT

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

Burn Lewis resolved UIMA-5117.
    Resolution: Fixed

Log errors at SEVERE level.  Use a shutdown hook to report when saxon calls exit.  Fix the
"net.sf.saxon.event.MessageEmitter is not a Receiver" error by not using a classloader if
saxon is already in the classpath

> UIMA-AS: dd2spring should log at INFO
> -------------------------------------
>                 Key: UIMA-5117
>                 URL: https://issues.apache.org/jira/browse/UIMA-5117
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>            Reporter: Jerry Cwiklik
>            Assignee: Burn Lewis
>             Fix For: 2.9.0AS
> Dd2Spring.convertDd2Spring() method should log exceptions at INFO level instead of CONFIG.
When runtime was mis-configured, the code was failing yet there were no exceptions being logged,
making debugging difficult.
> Also, when exception happens in converDd2Spring() it is not being re-thrown. This causes
the uima-as to continue running and trying to deploy using zero-length spring context file
which results in another Exception. Modify code to re-throw Exception.

This message was sent by Atlassian JIRA

View raw message