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/04/16 08:07:16 UTC
[jira] [Resolved] (LOG4J2-198) log4j2 stops application from
shutting down if the FlumeAppender is being used
[ https://issues.apache.org/jira/browse/LOG4J2-198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ralph Goers resolved LOG4J2-198.
--------------------------------
Resolution: Fixed
Fix Version/s: 2.0-beta5
Assignee: Ralph Goers
Fixed in revision 1468306 by changing FlumeAvroManager to use Flume's RPCClient. Please verify and close.
> log4j2 stops application from shutting down if the FlumeAppender is being used
> ------------------------------------------------------------------------------
>
> Key: LOG4J2-198
> URL: https://issues.apache.org/jira/browse/LOG4J2-198
> Project: Log4j 2
> Issue Type: Bug
> Components: Flume Appender
> Affects Versions: 2.0-beta5
> Reporter: offbynull
> Assignee: Ralph Goers
> Fix For: 2.0-beta5
>
> Attachments: zzzzzzzzzzzzzzzzzTest.tar.gz
>
>
> Steps to reproduce (use attached Maven project):
> 1. Start your remote flume agent
> 2. Run the Maven project and attach to it with the debugger in your favourite IDE (I use NetBeans)
> 3. Quickly 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 is named 'Avro NettyTransceiver I/O Worker 1' .
--
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