[
https://issues.apache.org/jira/browse/LOG4J2-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers resolved LOG4J2-265.
--------------------------------
Resolution: Won't Fix
There is no way to fix this issue in the Flume Appender. It must be fixed in
Flume.
> 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.zip
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
