[jira] [Updated] (LOG4J2-2972) AsyncAppender thread gets killed with ThreadDeath exception

["Volkan Yazici (Jira)" <ji...@apache.org>]

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

Volkan Yazici updated LOG4J2-2972:
----------------------------------
    Fix Version/s: 3.0.0

> AsyncAppender thread gets killed with ThreadDeath exception
> -----------------------------------------------------------
>
>                 Key: LOG4J2-2972
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-2972
>             Project: Log4j 2
>          Issue Type: Bug
>    Affects Versions: 2.14.0
>            Reporter: Volkan Yazici
>            Assignee: Volkan Yazici
>            Priority: Major
>             Fix For: 3.0.0, 2.14.1
>
>
> The fix we have introduced ~1 month ago to avoid \{{AsyncAppender}} thread getting killed, [introduces another problem|https://github.com/apache/logging-log4j2/commit/56436ad2176eac000d2821690e4373f097b76670#commitcomment-44892412]. In a nutshell, when the thread gets killed via \{{Thread#stop()}} it throws a \{{ThreadDeath}} exception which we unintentionally swallow, whereas the thread needs to be re-spawned again.
> This story aims to replace the custom \{{Thread}} usage with a single-threaded \{{Executor}}, which takes care of re-spawning.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)