[
https://issues.apache.org/jira/browse/LOG4J2-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13721797#comment-13721797
]
Remko Popma commented on LOG4J2-321:
------------------------------------
From: Ralph Goers
To: Log4J Developers List <log4j-dev@logging.apache.org>
Sent: Wednesday, July 24, 2013 7:57 AM
Subject: Re: Config additions, WAS: Confused: want low latency: do I need BOTH
async logger AND async appender??
I think I just came up with another attribute for the JMX element. I'll have
to look at the status logger but I believe it is always creating a StatusData
object and putting it in a ring buffer so they can be printed later. This will
actually create a lot of objects and will impact performance. So we will want
to add a statusLevel attribute to the JMX element to specify what the level is
on the events that should be added to the buffer.
It was actually kind of cool though as the person doing the performance test
looked at the JMX stats and even though the status was set to error in the
configuration they had lots of debug messages in JMX that were quite helpful to
verify a misconfiguration.
Ralph
> Provide configuration alternative to system properties
> ------------------------------------------------------
>
> Key: LOG4J2-321
> URL: https://issues.apache.org/jira/browse/LOG4J2-321
> Project: Log4j 2
> Issue Type: Bug
> Affects Versions: 2.0-beta8
> Reporter: Remko Popma
> Fix For: 2.0-beta9
>
>
> Some components behaviour cannot be configured in the configuration file but
> only with System properties. There is a strong preference to ensure all
> behaviour can be configured in the configuration file.
> Properties that can be used to configure AsyncLoggers when all loggers are
> Async:
> *
> Log4jContextSelector=org.apache.logging.log4j.core.async.AsyncLoggerContextSelector
> * AsyncLogger.ExceptionHandler
> * AsyncLogger.RingBufferSize
> * AsyncLogger.WaitStrategy
> * log4j.Clock - currently only used for timestamping RingBufferLogEvents.
> Question: Should all LogEvents use this clock?
> The following system properties can be used to configure mixed Async Loggers:
> * AsyncLoggerConfig.ExceptionHandler
> * AsyncLoggerConfig.RingBufferSize
> * AsyncLoggerConfig.WaitStrategy
> For JMX there is only the one "disable" property, in the mailing list it was
> suggested to make this into an element rather than an attribute to
> future-proof it.
--
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-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
