[
https://issues.apache.org/jira/browse/NIFI-6806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16959299#comment-16959299
]
ASF subversion and git services commented on NIFI-6806:
-------------------------------------------------------
Commit 8079d2531e561ad5dbbfe9e8dc4b818d694d57a6 in nifi's branch
refs/heads/master from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=8079d25 ]
NIFI-6805, NIFI-6806: Updated toString() of StandardControllerServiceNode so
that it includes the component's type and UUID, updated the more generic
Exception Mappers to include stack traces regardless of the log level that is
enabled
This closes #3840
Signed-off-by: Mike Thomsen <mthom...@apache.org>
> IllegalStateExceptionMapper, etc. should always log full stack trace
> --------------------------------------------------------------------
>
> Key: NIFI-6806
> URL: https://issues.apache.org/jira/browse/NIFI-6806
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Fix For: 1.11.0
>
>
> The IllegalStateExceptionMapper is used when any IllegalStateException makes
> its way all the way back to the web tier. This happens, for instance, if a
> Controller Service cannot be enabled. When this happens, the Exception Mapper
> only logs the stack trace if DEBUG is enabled. This is an old pattern that
> was followed during early releases to prevent such verbose logging, but this
> Exception Mapper needs to be updated to always log the stack traces.
> Otherwise, we have no way of knowing the underlying cause of the failure.
> IllegalArgumentExceptionMapper and a few others also appear to follow this
> same pattern and need to be updated.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
