You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Ralph Goers (JIRA)" <ji...@apache.org> on 2013/07/10 01:31:50 UTC
[jira] [Resolved] (LOG4J2-300) Flume Appender Persistent Manager
writer thread dies when Flume cannot connect to any agents
[ https://issues.apache.org/jira/browse/LOG4J2-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ralph Goers resolved LOG4J2-300.
--------------------------------
Resolution: Fixed
Fixed in revision 1501611.
> Flume Appender Persistent Manager writer thread dies when Flume cannot connect to any agents
> --------------------------------------------------------------------------------------------
>
> Key: LOG4J2-300
> URL: https://issues.apache.org/jira/browse/LOG4J2-300
> Project: Log4j 2
> Issue Type: Bug
> Components: Flume Appender
> Affects Versions: 2.0-beta7
> Reporter: Ralph Goers
> Assignee: Ralph Goers
> Fix For: 2.0-beta8
>
>
> FlumePeristentManager's WriterThread catches the exception thrown from the Flume RPCClient and then breaks out of the while loop causing the thread to stop. However, it does not mark the thread as shut down so subsequent events will be added to the Berkeley DB database and the key will be added to the internal queue. Eventually the queue will grow and cause an OutOfMemoryError.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org