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 "Ralph Goers (JIRA)" <ji...@apache.org> on 2014/09/11 04:55:35 UTC

[jira] [Commented] (LOG4J2-821) CompositeTriggeringPolicy behavior

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

Ralph Goers commented on LOG4J2-821:
------------------------------------

In short, no. If you configure a size-based trigger or a time-based trigger you want the rollover to happen when one of them occurs, not both.  That said, it should be possible to add an attribute to the CompositeTriggeringPolicy to indicate whether it should perform an and or an or.

> CompositeTriggeringPolicy behavior
> ----------------------------------
>
>                 Key: LOG4J2-821
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-821
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Appenders
>    Affects Versions: 2.0.2
>            Reporter: Hassan Kalaldeh
>
> referring to "Composite Triggering Policy" section under http://logging.apache.org/log4j/2.x/manual/appenders.html
> "Composite Triggering Policy
> The CompositeTriggeringPolicy combines multiple triggering policies and returns true if any of the configured policies return true. The CompositeTriggeringPolicy is configured simply by wrapping other policies in a Policies element."
> Shouldn't be the opposite, CompositeTriggeringPolicy  returns true only of all children triggering policies are met ?



--
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