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] [Commented] (UIMA-5117) UIMA-AS: dd2spring should log at INFO
Date Thu, 22 Sep 2016 20:00:25 GMT

    [ https://issues.apache.org/jira/browse/UIMA-5117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15514328#comment-15514328

Burn Lewis commented on UIMA-5117:

Since this is a serious error shouldn't we log at SEVERE rather than INFO?  Also no need to
catch the 3 specific exceptions since we log the same message ... just Exception would be

But in the case that triggered this investigation the log level didn't matter as even the
stack trace was not printed, apparently because saxon calls System.exit() on some errors.
 It also prints a cryptic error message "net.sf.saxon.event.MessageEmitter is not a Receiver"
that for some reason is not always captured.  The real problem is that UIMA-AS uses a classloader
to load the Transform class from saxon8.jar but if that jar is also in the users's classpath
there will be an incompatibility between classes loaded from each jar making it appear that
the MessageEmiiter class does not implement the Receiver interface.  We should omit the special
classloader if saxon8 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: Jerry Cwiklik
>             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