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

Gary ,Verwers commented on LOG4J2-3619:
---------------------------------------

I have tried to create an example application that does the StackOverflowError 
but I have not been successful in getting the process to stall.   We have two 
different scenarios which the logging stalls when logging a StackOverflowError. 
   I think it may be the combination of StackOverflowError and a very large 
message.   But my test application is not stalling.   If I can create 
repeatable test I will post it. 

> 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
>         Attachments: BatchEventProcessor.png, CauseEvent.png, 
> IncomingReferences.png, cusor.png, gatinngSequence.png, log4j2.xml, 
> thread-dump-analyses.png, threadDump.txt
>
>
> 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)

Reply via email to