[jira] [Resolved] (LOG4J2-867) FlumeAppender: maxDelay not in seconds, but milliseconds

["Gary Gregory (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/LOG4J2-867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Gregory resolved LOG4J2-867.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 2.1

Fix pushed to master. 

Please verify and close.

> FlumeAppender: maxDelay not in seconds, but milliseconds
> --------------------------------------------------------
>
>                 Key: LOG4J2-867
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-867
>             Project: Log4j 2
>          Issue Type: Documentation
>          Components: Appenders
>    Affects Versions: 2.0.2
>            Reporter: Simon Broeng Jensen
>            Priority: Minor
>             Fix For: 2.1
>
>
> 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



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org