You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@logging.apache.org by "Volkan Yazici (Jira)" <ji...@apache.org> on 2022/10/14 09:09:00 UTC

[jira] [Commented] (LOG4J2-3619) Log4j stops logging when the log message contains a java.lang.StackOverflowError

    [ https://issues.apache.org/jira/browse/LOG4J2-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17617587#comment-17617587 ] 

Volkan Yazici commented on LOG4J2-3619:
---------------------------------------

[~gverwers], mind sharing some more details, please? The configuration you are using, the stacktrace you are getting prior to RingBuffer halt, etc.


> Log4j stops logging when the log message contains a java.lang.StackOverflowError
> --------------------------------------------------------------------------------
>
>                 Key: LOG4J2-3619
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-3619
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.17.2
>         Environment: We run Weblogic 12 in a Linux environment.  
>            Reporter: Gary ,Verwers
>            Priority: Major
>
> The RingBuffer Consumer stop printing logs when it comes to a log event with an exception connected with a StackOverFlowError attached.    We have had this occur several dozen times.
> Both the cursor and the gate point at the same place in the event buffer and very quickly all the threads on the server are frozen waiting for the ring buffer to clear up space.   But the consumer is just stuck waiting a not printing event.   It has failed with a stack overflow from spring MVC mapping and it has failed with a stack overflow from Jackson JSON ObjectMapper with object level recursion triggering a stack overflow.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)