[
https://issues.apache.org/jira/browse/UIMA-5117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jerry Cwiklik updated UIMA-5117:
--------------------------------
Description:
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.
was:
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.
> 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
(v6.3.4#6332)
