[
https://issues.apache.org/jira/browse/LOG4J2-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14564924#comment-14564924
]
Remko Popma commented on LOG4J2-321:
------------------------------------
This Jira ticket has not been implemented yet.
Please refer to the Async Loggers documentation on how to enable Async Logging.
Using <AsyncLogger> in the configuration is one way. Please see the manual for
details.
> 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
> Assignee: Remko Popma
> Fix For: 2.3
>
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
