[LOG4J2-321] Provide configuration alternative to system properties

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 2.0-beta8
• Assignee: Remko Popma
• Reporter: Remko Popma
• Created: 27/Jul/13 23:28
• Updated: 04/Oct/16 08:03
• Resolved: 04/Oct/16 08:03

Description

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.

Issue Links

• relates to: LOG4J2-329 StatusLogger creates many objects with no way to limit them
• relates to: LOG4J2-396 Disable JMX by default