You are viewing a plain text version of this content. The canonical link for it is here.

Posted to log4j-dev@logging.apache.org by "Simon Broeng Jensen (JIRA)" <ji...@apache.org> on 2014/10/03 14:34:33 UTC

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

Simon Broeng Jensen created LOG4J2-867:
------------------------------------------

             Summary: FlumeAppender: maxDelay not in seconds, but miliseconds
                 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


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