logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ralph Goers (JIRA)" <j...@apache.org>
Subject [jira] [Created] (LOG4J2-300) Flume Appender Persistent Manager writer thread dies when Flume cannot connect to any agents
Date Mon, 08 Jul 2013 21:19:49 GMT
Ralph Goers created LOG4J2-300:
----------------------------------

             Summary: 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
             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


Mime
View raw message