You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Gena Svarovski (Jira)" <ji...@apache.org> on 2020/01/24 12:44:00 UTC
[jira] [Commented] (LOG4J2-2765) Log4j2 async logger threads are
locked on WAITING
[ https://issues.apache.org/jira/browse/LOG4J2-2765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17022910#comment-17022910 ]
Gena Svarovski commented on LOG4J2-2765:
----------------------------------------
Some more details about this problem.
We have quite intensive logging. 1700 lines per second (1300 to main log), 400k per second (300k to main log) daily average with bigger values during peak times.
There is separate 10T SSD raid for logs and it is about 50% occupied. When most application threads were blocked and not responding to external requests, background threads continued working and were able to log their actions. So, disk failure can be excluded.
Also, there's nothing for that time in `/var/log/messages`.
We do not have `log4j2.contextSelector` property set.
Please let me know what else info can be useful.
> Log4j2 async logger threads are locked on WAITING
> -------------------------------------------------
>
> Key: LOG4J2-2765
> URL: https://issues.apache.org/jira/browse/LOG4J2-2765
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.6.2
> Environment: CentOS 6.10
> JVM 1.8.0-zing_19.05.101.0
> Reporter: Gena Svarovski
> Priority: Major
> Attachments: log4j2-sample.xml, threads-123948-20200115-155247-short.txt
>
>
> Recently our server stopped responding and from thread dump we found that most threads are blocked in "WAITING (parking)" state on logging. Any advises are welcome.
> Attaching selected threads dump and log4j.xml
--
This message was sent by Atlassian Jira
(v8.3.4#803005)