[jira] [Updated] (LOG4J2-197) log4j2 creates 2 threads per each log attempt if the remote flume agent goes down

[ https://issues.apache.org/jira/browse/LOG4J2-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] offbynull updated LOG4J2-197: - Fix Version/s: (was: 2.0-beta5) Affects Version/s: 2.0-beta5 > log4j2 creates 2 threads p

[jira] [Updated] (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 ] offbynull updated LOG4J2-198: - Description: Steps to reproduce (use attached Maven project): 1. Start your remote flume agent 2. Run th

[jira] [Updated] (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 ] offbynull updated LOG4J2-198: - Attachment: zTest.tar.gz Attached Maven project required for repo steps.

[jira] [Created] (LOG4J2-198) log4j2 stops application from shutting down if the FlumeAppender loses its connection to the remote flume agent

offbynull created LOG4J2-198: Summary: log4j2 stops application from shutting down if the FlumeAppender loses its connection to the remote flume agent Key: LOG4J2-198 URL: https://issues.apache.org/jira/browse/LOG4J2-

[jira] [Updated] (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 ] offbynull updated LOG4J2-198: - Summary: log4j2 stops application from shutting down if the FlumeAppender is being used (was: log4j2 sto

[jira] [Updated] (LOG4J2-197) log4j2 creates 2 threads per each log attempt if the remote flume agent goes down

[ https://issues.apache.org/jira/browse/LOG4J2-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] offbynull updated LOG4J2-197: - Description: Steps to reproduce (use attached Maven project): 1. Start your remote flume agent 2. Run th

[jira] [Updated] (LOG4J2-196) log4j2 blocks on logging calls if the FlumeAppender loses its connection to the remote flume agent

[ https://issues.apache.org/jira/browse/LOG4J2-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] offbynull updated LOG4J2-196: - Description: Steps to reproduce (use attached Maven project): 1. Start your remote flume agent 2. Run th

[jira] [Updated] (LOG4J2-197) log4j2 creates 2 threads per each log attempt if the remote flume agent goes down

[ https://issues.apache.org/jira/browse/LOG4J2-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] offbynull updated LOG4J2-197: - Description: Steps to reproduce (use attachmented Maven project): 1. Start your remote flume agent 2. Ru

[jira] [Updated] (LOG4J2-197) log4j2 creates 2 threads per each log attempt if the remote flume agent goes down

[ https://issues.apache.org/jira/browse/LOG4J2-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] offbynull updated LOG4J2-197: - Attachment: Screenshot.png zTest.tar.gz Attached Maven project required f

[jira] [Updated] (LOG4J2-197) log4j2 creates 2 threads per each log attempt if the remote flume agent goes down

[ https://issues.apache.org/jira/browse/LOG4J2-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] offbynull updated LOG4J2-197: - Description: Steps to reproduce (use attachmented Maven project): 1. Start your remote flume agent 2. Ru

[jira] [Updated] (LOG4J2-197) log4j2 creates 2 threads per each log attempt if the remote flume agent goes down

[ https://issues.apache.org/jira/browse/LOG4J2-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] offbynull updated LOG4J2-197: - Description: Steps to reproduce (use attachmented Maven project): 1. Start your remote flume agent 2. Ru

[jira] [Created] (LOG4J2-197) log4j2 creates 2 threads per each log attempt if the remote flume agent goes down

offbynull created LOG4J2-197: Summary: log4j2 creates 2 threads per each log attempt if the remote flume agent goes down Key: LOG4J2-197 URL: https://issues.apache.org/jira/browse/LOG4J2-197 Project: Log4

[jira] [Updated] (LOG4J2-196) log4j2 blocks on logging calls if the FlumeAppender loses its connection to the remote flume agent

[ https://issues.apache.org/jira/browse/LOG4J2-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] offbynull updated LOG4J2-196: - Description: Steps to reproduce (use attachmented Maven project): 1. Start your remote flume agent 2. Ru

[jira] [Updated] (LOG4J2-196) log4j2 blocks on logging calls if the FlumeAppender loses its connection to the remote flume agent

[ https://issues.apache.org/jira/browse/LOG4J2-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] offbynull updated LOG4J2-196: - Description: Steps to reproduce (use attachmented Maven project): 1. Start your remote flume agent 2. Ru

[jira] [Updated] (LOG4J2-196) log4j2 blocks on logging calls if the FlumeAppender loses its connection to the remote flume agent

[ https://issues.apache.org/jira/browse/LOG4J2-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] offbynull updated LOG4J2-196: - Description: Steps to reproduce (use attachmented Maven project): 1. Start your remote flume agent 2. Ru

[jira] [Created] (LOG4J2-196) log4j2 blocks on logging calls if the FlumeAppender loses its connection to the remote flume agent

offbynull created LOG4J2-196: Summary: log4j2 blocks on logging calls if the FlumeAppender loses its connection to the remote flume agent Key: LOG4J2-196 URL: https://issues.apache.org/jira/browse/LOG4J2-196

[jira] [Updated] (LOG4J2-196) log4j2 blocks on logging calls if the FlumeAppender loses its connection to the remote flume agent

[ https://issues.apache.org/jira/browse/LOG4J2-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] offbynull updated LOG4J2-196: - Attachment: zTest.tar.gz Attached Maven project required for the reproduction steps.

Re: JMX support in log4j2

Hey, I just thought of another JMX feature: the ability to "flushBuffers". This is something that I've wanted for years in log4j1: to reduce the logging performance penalty I usually use buffered IO with immediateFlush=false. That gives good performance, but the drawback is that if you want to

Re: JMX support in log4j2

Fine, but let's not end up with another 479k jar (like Log4j-1.2.17) all in the name of "fewer jars".  Again, the option of an uber jar is fine for those who don't care about bloating their application.  But for those who want to use Log4j2 purely for logging in their application, let's keep i