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

Install default error handler for Async Loggers that does not rethrow (was: Async Logger - Consumer thread dying - new thread unable to start)

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 2.2
    • 2.6
    • Core
    • None
    • LOG4J CORE Release Version 2.2
      Disruptor Bundle-Version 3.3.2
      ORACLE jdk1.8.0_45
      Linux 2.6.32-573.el6.x86_64, amd64

    Description

      We are seeing a situation where the consumer thread
      "AsyncLoggerConfig-1" is apparently dying.
      We do see a new consumer thread trying to start up, but it is blocked
      waiting for a lock, so no logging is happening.

      Is this a defect in log4j?
      Is the original consumer thread dying due to perhaps an unhandled exception ?
      Is that original consumer thread not terminating gracefully and
      releasing the locked object so the new consumer thread can start?

      Please see attached screenshot. Top of screen is normal
      asyncloggerconfig thread (consumer).
      Bottom is thread trace when logging stops, we no longer see an
      "asyncloggerconfig-1" thread, instead a new thread is trying to start
      but never does "asyncloggerconfig-2".

      Attachments

        1. 2016-03-18_17-44-06.jpg
          297 kB
          Steve Yurong Su
        2. 2016-03-22_8-32-37.jpg
          94 kB
          Steve Yurong Su
        3. BatchEventProcessor.png
          63 kB
          Steve Yurong Su
        4. log4j2_config.xml
          14 kB
          Steve Yurong Su

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            rpopma Remko Popma
            rong Steve Yurong Su
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment