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 "Jim Tang (JIRA)" <ji...@apache.org> on 2013/05/23 17:03:19 UTC
[jira] [Created] (LOG4J2-265) FlumeAppender Stops App from Shutting
Down when Newer Version of Netty is Used
Jim Tang created LOG4J2-265:
-------------------------------
Summary: FlumeAppender Stops App from Shutting Down when Newer Version of Netty is Used
Key: LOG4J2-265
URL: https://issues.apache.org/jira/browse/LOG4J2-265
Project: Log4j 2
Issue Type: Bug
Components: Appenders
Affects Versions: 2.0-beta6
Reporter: Jim Tang
Attachments: zzzzzzzzzzzzzzzzzTest.7z
FlumeAppender(log4j-flume-ng) depends on flume-ng-sdk, which uses netty-3.4.0.Final. When a higher version of netty is used instead, such as 3.5.8.Final or 3.6.5.Final, FlumeAppender will not shutdown properly.
To reproduce the problem (use attached Maven project):
1. Start your remote flume agent
2. Change the log4j2.xml to your agent host and port
3. press x and hit Enter
Notice how the application continues to run. Press x should break out of the main loop and return from main(), indicating that the application should close.
The thread holding things up are
Hashed wheel timer #1
New I/O worker #1-8
--
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