[
https://issues.apache.org/jira/browse/NIFI-1447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15124078#comment-15124078
]
ASF subversion and git services commented on NIFI-1447:
-------------------------------------------------------
Commit 807eb8de6d7054cef1fac91cbf2e2a1eb37d30ed in nifi's branch
refs/heads/master from [~ozhurakousky]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=807eb8d ]
NIFI-1447 modified SimpleProcessLogger Modified SimpleProcessLogger to ensure
that whenever is called it prints full stack trace.
Signed-off-by: jpercivall <[email protected]>
> Improve exception logging for Processors
> ----------------------------------------
>
> Key: NIFI-1447
> URL: https://issues.apache.org/jira/browse/NIFI-1447
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Oleg Zhurakousky
> Assignee: Oleg Zhurakousky
> Fix For: 0.5.0
>
>
> Unfortunately while the title says _"improve"_, I am logging it as a BUG for
> the following reasons.
> A client reported an issue with one of the processors where the only visible
> message in both _bulletin and logs_ is the message produced by ProcessLogger
> which does not seem to log a full stack trace. A typical pattern in current
> processor implementation is to have a significant code in _onTrigger()_
> method to be wrapped in _try/catch_ where exception is logged and then
> re-thrown. Unfortunately it's not the case for this particular processor. As
> a result it is impossible to determine the cause of the root problem.
> While immediate solution is to modify the specific Processor by wrapping its
> significant code in _try/catch_ a better solution would be to improve
> ProcessLogger to log full stack trace whenever there is an error.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
