[
https://issues.apache.org/jira/browse/LOG4J2-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17171702#comment-17171702
]
Denis Orlov commented on LOG4J2-2816:
-------------------------------------
A couple of recent NPEs that I found in our logs, might be they give you some
clue:
{code}
85421.099: [purging class loader data graph, 0.0000004 secs]
AsyncLogger error handling event seq=2562707,
value='org.apache.logging.log4j.core.async.RingBufferLogEvent@8349151':
java.lang.NullPointerException: null
java.lang.NullPointerException
at
org.apache.logging.log4j.core.async.RingBufferLogEvent.execute(RingBufferLogEvent.java:154)
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=2562719,
value='org.apache.logging.log4j.core.async.RingBufferLogEvent@14ce32ee':
java.lang.NullPointerException: null
java.lang.NullPointerException
at
org.apache.logging.log4j.core.async.RingBufferLogEvent.execute(RingBufferLogEvent.java:154)
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)
85422.099: [deflating idle monitors, 0.0000709 secs]
{code}
and
{code}
255084.625: [purging class loader data graph, 0.0000004 secs]
vmop [threads: total initially_running
wait_to_block] [time: spin block sync cleanup vmop] page_trap_count
255034.094: no vm operation [ 160 0
0 ] [ 0 0 0 0 0 ] 0
255036.344: RevokeBias [ 161 0
0 ] [ 0 0 0 0 0 ] 0
255044.359: no vm operation [ 161 1
1 ] [ 0 0 0 0 0 ] 0
255051.359: RevokeBias [ 161 0
0 ] [ 0 0 0 0 0 ] 0
255084.625: GenCollectForAllocation [ 161 0
0 ] [ 0 0 0 0 10 ] 0
255086.636: [deflating idle monitors, 0.0001007 secs]
255086.637: [updating inline caches, 0.0000419 secs]
255086.637: [compilation policy safepoint handler, 0.0003801 secs]
255086.637: [mark nmethods, 0.0002247 secs]
255086.637: [purging class loader data graph, 0.0000005 secs]
[Loaded org.slf4j.helpers.MessageFormatter from
file:/export/log/data/acesp3/apps/components/ms_sor_fx_nyc_prod_01/releases/FX-7.4.3/lib/slf4j-api-1.7.28.jar]
[Loaded org.slf4j.helpers.FormattingTuple from
file:/export/log/data/acesp3/apps/components/ms_sor_fx_nyc_prod_01/releases/FX-7.4.3/lib/slf4j-api-1.7.28.jar]
AsyncLogger error handling event seq=7871233,
value='org.apache.logging.log4j.core.async.RingBufferLogEvent@51f29583':
java.lang.NullPointerException: null
java.lang.NullPointerException
255091.641: [deflating idle monitors, 0.0000797 secs]
{code}
"Loaded org.slf4j.helpers.MessageFormatter" from last NPE report might give you
some hints.
> NullPointerException from AsyncLogger
> -------------------------------------
>
> Key: LOG4J2-2816
> URL: https://issues.apache.org/jira/browse/LOG4J2-2816
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.13.0
> Reporter: Denis
> Priority: Minor
>
> We've got several times following NullPointerException (example from our
> stdout.log):
>
> {code:java}
> 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]
> {code}
>
> What is interesting this NPEs always preceeded by
> {code}
> 84449.232: [purging class loader data graph, 0.0000003 secs] vm message
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
