Uploaded image for project: 'Log4j 2'
  1. Log4j 2
  2. LOG4J2-2972

AsyncAppender thread gets killed with ThreadDeath exception

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 2.14.0
    • 3.0.0, 2.14.1
    • None
    • None

    Description

      The fix we have introduced ~1 month ago to avoid AsyncAppender thread getting killed, introduces another problem. 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.

      Attachments

        Issue Links

          Activity

            People

              vy Volkan Yazici
              vy Volkan Yazici
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: