[ 
https://issues.apache.org/jira/browse/LOG4J2-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13637136#comment-13637136
 ] 

Ralph Goers commented on LOG4J2-173:
------------------------------------

I've looked at your test and I'm not sure the BurstFilter works the way you 
think it does.  When you set the level to info all warn and error messages 
should go through without being blocked (they are not subject to burst 
filtering). Events at info, debug, trace, etc are allowed through so long as 
they don't exceed the burst limit.  Your changes to the test seem to expect to 
filter all events below the specified level and do burst filtering on events 
above it.
                
> BurstFilter does not honour level
> ---------------------------------
>
>                 Key: LOG4J2-173
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-173
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Filters
>    Affects Versions: 2.0-beta4
>            Reporter: Henry Clout
>         Attachments: BurstFilterTest.java
>
>
> I've been getting info (and below) logging out of the BurstFilter despite it 
> being set to warn.  The problem seems to be in the filter method, the test :
> if (this.level.isAtLeastAsSpecificAs(level)) {
> ... seems to be the wrong way around.
> I changed the method locally to be:
>     private Result filter(final Level level) {
>         if (level.isAtLeastAsSpecificAs(this.level)) {
>             LogDelay delay = history.poll();
>             while (delay != null) {
>                 available.add(delay);
>                 delay = history.poll();
>             }
>             delay = available.poll();
>             if (delay != null) {
>                 delay.setDelay(burstInterval);
>                 history.add(delay);
>                 return onMatch;
>             }
>             return onMismatch;
>         }
>         return onMismatch;
>     }
> Which seems to have the desired results.
> Does this make sense?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

Reply via email to