[
https://issues.apache.org/jira/browse/LOG4J2-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17171698#comment-17171698
]
Denis Orlov commented on LOG4J2-2816:
-------------------------------------
Sorry for such long silence. Other more urgent tasks poped up.
Here is Details you asked:
We observer that NPEs from AcynLogger both on Solaris:
{code}
# cat /etc/release
Solaris 10 10/09 s10x_u8wos_08a X86
Copyright 2009 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 16 September 2009
Solaris 10 1/13 (Update 11) Patchset applied.
{code}
/current/lib# ls | grep disruptor
disruptor-3.4.2.jar
{code}
stdout.log:
{code}
-XX:+AlwaysPreTouch -XX:+CMSConcurrentMTEnabled
-XX:CMSInitiatingOccupancyFraction=80 -XX:+CMSScavengeBeforeRemark
-XX:CompileThreshold=100 -XX:CompressedClassSpaceSize=260046848
-XX:+ExitOnOutOfMemoryError -XX:+ExplicitGCInvokesConcurrentAndUnloadsClasses
-XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=logs/heap.dmp
-XX:InitialHeapSize=2147483648 -XX:InitialTenuringThreshold=8
-XX:+ManagementServer -XX:MaxHeapSize=2147483648 -XX:MaxMetaspaceSize=268435456
-XX:MaxNewSize=1073741824 -XX:MaxTenuringThreshold=15
-XX:MetaspaceSize=268435456 -XX:NewSize=1073741824 -XX:OldPLABSize=16
-XX:+OptimizeStringConcat -XX:+ParallelRefProcEnabled
-XX:+PrintAdaptiveSizePolicy -XX:+PrintCMSInitiationStatistics
-XX:PrintCMSStatistics=2 -XX:+PrintCommandLineFlags -XX:+PrintFlagsFinal
-XX:+PrintGC -XX:+PrintGCApplicationConcurrentTime
-XX:+PrintGCApplicationStoppedTime -XX:+PrintGCCause -XX:+PrintGCDateStamps
-XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+PrintHeapAtGC
-XX:+PrintHeapAtSIGBREAK -XX:+PrintJNIGCStalls -XX:+PrintPromotionFailure
-XX:+PrintReferenceGC -XX:+PrintSafepointStatistics
-XX:PrintSafepointStatisticsCount=5 -XX:+PrintTLAB
-XX:+PrintTenuringDistribution -XX:+ScavengeBeforeFullGC -XX:SurvivorRatio=6
-XX:TargetSurvivorRatio=90 -XX:-TieredCompilation -XX:+TraceClassLoading
-XX:+TraceClassUnloading -XX:+TraceSafepointCleanupTime
-XX:+UnlockDiagnosticVMOptions -XX:+UseCMSInitiatingOccupancyOnly
-XX:+UseCompressedClassPointers -XX:+UseCompressedOops -XX:+UseConcMarkSweepGC
-XX:+UseLargePages -XX:+UseLargePagesInMetaspace -XX:+UseParNewGC
[Opened
/export/log/data/acesp3/home/lib/jdk/openjdk-1.8.0_221-99/jre/lib/rt.jar]
{code}
And on Linux:
{code}
> cat /etc/os-release
NAME="SLES"
VERSION="11.4"
VERSION_ID="11.4"
PRETTY_NAME="SUSE Linux Enterprise Server 11 SP4"
ID="sles"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:suse:sles:11:4"
{code}
Stdout fragment with JDK verison:
{code}
[Opened /home/acesp3/lib/jdk/openjdk-1.8.0_221-89/jre/lib/rt.jar]
{code}
> 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)
