You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Ralph Goers (Jira)" <ji...@apache.org> on 2020/06/28 03:05:00 UTC
[jira] [Commented] (LOG4J2-2880) High CPU consumption using
StackWalker
[ https://issues.apache.org/jira/browse/LOG4J2-2880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17147165#comment-17147165 ]
Ralph Goers commented on LOG4J2-2880:
-------------------------------------
There is not enough information here to be able to do any problem determination. That said, I suspect this is a duplicate of https://issues.apache.org/jira/browse/LOG4J2-2792. Please review that issue and see if it applies to your case. If not, please provide your logging configuration and, ideally, a sample program that demonstrates the problem.
> High CPU consumption using StackWalker
> --------------------------------------
>
> Key: LOG4J2-2880
> URL: https://issues.apache.org/jira/browse/LOG4J2-2880
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.11.1, 2.11.2, 2.12.0, 2.12.1, 2.13.0, 2.13.1, 2.13.2, 2.13.3
> Environment: log4j version: 2.12.1
> JDK version: OpenJDK 11.0.6
> Reporter: Hash Jang
> Priority: Major
> Attachments: image-2020-06-28-02-42-12-987.png
>
>
> While using OpenJDK 11, there are possibility cause severe CPU consumption because of JDK bug in using StackWalker.
>
> [Application on JDK11 consume 100% CPU after a few hours of uptime|[https://bugs.openjdk.java.net/browse/JDK-8222942]]
>
> And it happened serveral times on our production environment.
>
> !image-2020-06-28-02-42-12-987.png!
>
> Stack trace Is:
> "reactor-http-epoll-1" #75 daemon prio=5 os_prio=0 cpu=25100145.64ms elapsed=306507.26s tid=0x0000556eddcbd000 nid=0x61 runnable [0x00007f8605443000]"reactor-http-epoll-2" #75 daemon prio=5 os_prio=0 cpu=25100145.64ms elapsed=306507.26s tid=0x0000556eddcbd000 nid=0x61 runnable [0x00007f8605443000] java.lang.Thread.State: RUNNABLE at java.lang.StackStreamFactory$AbstractStackWalker.callStackWalk(java.base@11.0.6/Native Method) at java.lang.StackStreamFactory$AbstractStackWalker.beginStackWalk(java.base@11.0.6/StackStreamFactory.java:370) at java.lang.StackStreamFactory$AbstractStackWalker.walk(java.base@11.0.6/StackStreamFactory.java:243) at java.lang.StackWalker.walk(java.base@11.0.6/StackWalker.java:498) at org.apache.logging.log4j.util.StackLocator.calcLocation(StackLocator.java:81) at org.apache.logging.log4j.util.StackLocatorUtil.calcLocation(StackLocatorUtil.java:76) at org.apache.logging.log4j.spi.AbstractLogger.getLocation(AbstractLogger.java:2201) at org.apache.logging.log4j.spi.AbstractLogger.logMessageTrackRecursion(AbstractLogger.java:2144) at org.apache.logging.log4j.spi.AbstractLogger.logMessageSafely(AbstractLogger.java:2127) at org.apache.logging.log4j.spi.AbstractLogger.logMessage(AbstractLogger.java:2020) at org.apache.logging.log4j.spi.AbstractLogger.logIfEnabled(AbstractLogger.java:1891) at org.apache.logging.log4j.spi.AbstractLogger.info(AbstractLogger.java:1436)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)