Hi,
CronTriggeringPolicy does not work either. We started to send requests at
17:26, the vproxy_access.2017-02-06.17 was correctly created, and it rotated at
18:00. Ok.
But the vproxy_access. 2017-02-06.18 didn't rotate at 19:00. The last line is:
1,167.114.89.180,2017-06-02
19:59:59.969,A,56,
This sounds like a bug that has already been reported. I would suggest you try
the CronTriggeringPolicy instead o the TimeBasedTriggeringPolicy.
Ralph
> On Jun 2, 2017, at 3:19 AM, Joan Balagueró - ventusproxy
> wrote:
>
> Hello,
>
>
>
> I致e posted this in stackoverflow, with no success. S
Hello,
Ive posted this in stackoverflow, with no success. So Im trying here now.
I'm seeing the following behaviour in log4j2, not sure if it's the expected.
This is part of my log4j.xml:
%m%d{-MM-dd HH:mm:ss.SSS}%n
The log.rotateAccess is a sys