[logback-user] FixedWindowRollingPolicy has max 20?

[Dessie K]

Thanks,

Is there a reason max is set to 20. Is there a performance impact or other
reason 20 was chosen?


On Tue, Aug 12, 2014 at 4:49 PM, Gena Makhomed <gmm at csdoc.com> wrote:

> On 12.08.2014 18:16, Dessie K wrote:
>
>  I'm trying to have a large window size 200.
>>
>> But noticed it is fixed to max 20:
>>
>> https://github.com/qos-ch/logback/blob/master/logback-
>> core/src/main/java/ch/qos/logback/core/rolling/
>> FixedWindowRollingPolicy.java
>>
>> Why is 20 the max?
>> An is there anyway to force it to use a larger window size?
>>
>
> subclasses can override it:
>
> https://github.com/qos-ch/logback/blob/master/logback-
> core/src/main/java/ch/qos/logback/core/rolling/
> FixedWindowRollingPolicy.java
>
> /**
>    * Subclasses can override this method to increase the max window size,
> if required.  This is to
>    * address LOGBACK-266.
>    * @return
>    */
>   protected int getMaxWindowSize() {
>     return MAX_WINDOW_SIZE;
>   }
>
> or probably you just need
> http://logback.qos.ch/manual/appenders.html#SizeAndTimeBasedFNATP
>
> more details in http://jira.qos.ch/browse/LOGBACK-266
>
> --
> Best regards,
>  Gena
> _______________________________________________
> Logback-user mailing list
> Logback-user at qos.ch
> http://mailman.qos.ch/mailman/listinfo/logback-user
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.qos.ch/pipermail/logback-user/attachments/20140812/4df5bda9/attachment.html>