You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@logging.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2019/07/19 20:04:00 UTC

[jira] [Commented] (LOG4J2-2659) AbstractAction should catch and report RuntimeException and possibly Error

    [ https://issues.apache.org/jira/browse/LOG4J2-2659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16889161#comment-16889161 ] 

ASF subversion and git services commented on LOG4J2-2659:
---------------------------------------------------------

Commit 43add80dc20f1b9b177037a67a062fc598459c48 in logging-log4j2's branch refs/heads/release-2.x from Carter Kozak
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=43add80 ]

LOG4J2-2659: AbstractAction handles unchecked RuntimeException and Error (#297)



> AbstractAction should catch and report RuntimeException and possibly Error
> --------------------------------------------------------------------------
>
>                 Key: LOG4J2-2659
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-2659
>             Project: Log4j 2
>          Issue Type: Improvement
>    Affects Versions: 2.12.0
>            Reporter: Carter Kozak
>            Assignee: Carter Kozak
>            Priority: Major
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> Currently we only catch IOException, we should surface all failures the same way.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)