nifi-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Payne (Jira)" <j...@apache.org>
Subject [jira] [Updated] (NIFI-6806) IllegalStateExceptionMapper, etc. should always log full stack trace
Date Thu, 24 Oct 2019 15:45:00 GMT

     [ https://issues.apache.org/jira/browse/NIFI-6806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mark Payne updated NIFI-6806:
-----------------------------
    Fix Version/s: 1.11.0
           Status: Patch Available  (was: Open)

> 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)

Mime
View raw message