[
https://issues.apache.org/jira/browse/LOG4J2-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15233340#comment-15233340
]
Remko Popma edited comment on LOG4J2-1361 at 4/9/16 4:14 AM:
-------------------------------------------------------------
I suggest replacing AsyncAppender with [Async
Loggers|http://logging.apache.org/log4j/2.x/manual/async.html] since the latter
provide the ability to configure a custom error handler. This should allow you
to solve the problem.
was (Author: rem...@yahoo.com):
[Async Loggers|http://logging.apache.org/log4j/2.x/manual/async.html] provide
the ability to configure a custom error handler. This should allow you to solve
the problem.
> AsyncAppender never recovers from OutOfMemoryError in AsyncThread.run
> ---------------------------------------------------------------------
>
> Key: LOG4J2-1361
> URL: https://issues.apache.org/jira/browse/LOG4J2-1361
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
> Affects Versions: 2.5
> Reporter: Dan Berindei
>
> We have a test that allocates too much memory, causing {{OutOfMemoryError}}s
> for a short time.
> Because {{AsyncThread.run()}} doesn't handle them in any way, the thread
> exits, and all the logging threads block in {{AsyncAppender.append()}},
> hanging the test suite.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
