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

NullPointerException from AsyncLogger

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 2.13.0
    • Fix Version/s: 3.0.0, 2.15.0
    • Component/s: Core
    • Labels:
      None

      Description

      We've got several times following NullPointerException (example from our stdout.log):
       

      84449.232: [purging class loader data graph, 0.0000003 secs]
      AsyncLogger error handling event seq=1037012, value='org.apache.logging.log4j.core.async.RingBufferLogEvent@2a7b2d78': java.lang.NullPointerException: null
      java.lang.NullPointerException
       at org.apache.logging.log4j.core.async.RingBufferLogEvent.execute(RingBufferLogEvent.java:161)
       at org.apache.logging.log4j.core.async.RingBufferLogEventHandler.onEvent(RingBufferLogEventHandler.java:46)
       at org.apache.logging.log4j.core.async.RingBufferLogEventHandler.onEvent(RingBufferLogEventHandler.java:29)
       at com.lmax.disruptor.BatchEventProcessor.processEvents(BatchEventProcessor.java:168)
       at com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:125)
       at java.lang.Thread.run(Thread.java:748)
      AsyncLogger error handling event seq=1037022, value='org.apache.logging.log4j.core.async.RingBufferLogEvent@d5d330f': java.lang.NullPointerException: null
      java.lang.NullPointerException
       at org.apache.logging.log4j.core.async.RingBufferLogEvent.execute(RingBufferLogEvent.java:161)
       at org.apache.logging.log4j.core.async.RingBufferLogEventHandler.onEvent(RingBufferLogEventHandler.java:46)
       at org.apache.logging.log4j.core.async.RingBufferLogEventHandler.onEvent(RingBufferLogEventHandler.java:29)
       at com.lmax.disruptor.BatchEventProcessor.processEvents(BatchEventProcessor.java:168)
       at com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:125)
       at java.lang.Thread.run(Thread.java:748)
      84450.232: [deflating idle monitors, 0.0000624 secs]
      

       

      What is interesting this NPEs always preceeded by

      84449.232: [purging class loader data graph, 0.0000003 secs] vm message
      

        Attachments

          Activity

            People

            • Assignee:
              vy Volkan Yazici
              Reporter:
              orloden Denis
            • Votes:
              3 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: