[LOG4J2-867] FlumeAppender: maxDelay not in seconds, but milliseconds

• Type: Documentation
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.0.2
• Fix Version/s: 2.1
• Component/s: Appenders
• Assignee: Unassigned
• Reporter: Simon Broeng Jensen
• Created: 03/Oct/14 12:33
• Updated: 13/Oct/14 12:33
• Resolved: 03/Oct/14 22:49

Description

Hi,

We are using FlumeAppender with Log4j2, version 2.0.2.

The documentation, and javadoc, specifies maxDelay as using seconds, but it's actually used as milliseconds (see FlumePersistentManager).

We would suggest updating the javadoc, and documentation at:
https://logging.apache.org/log4j/2.x/manual/appenders.html#FlumeAppender