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/09/22 21:33:20 UTC

[jira] [Resolved] (UIMA-5117) UIMA-AS: dd2spring should log at INFO

     [ 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
(v6.3.4#6332)