SizeBasedTriggeringPolicy counter not resetting after TimeBasedTriggeringPolicy rollover #1842
Replies: 5 comments 2 replies
-
@rgoers, can you take a look at this? |
Beta Was this translation helpful? Give feedback.
-
Hello. Was wondering if there is some update on this? The behavior seems to conflict with log4j documentation. Thank you. |
Beta Was this translation helpful? Give feedback.
-
I think It is not a bug. If app still run then %i will increase. If app restarts %i = 1. When I see these fileName with %i=1 , I can known when app start/stop easily. but you should change config as following (-1 means max of %i = Max of Integer ): |
Beta Was this translation helpful? Give feedback.
-
It is a bug. I created #2297 to fix it. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Hello. Using log4j 2.20.0. My configuration file specifies a SizeBasedTriggeringPolicy and a TimeBasedTriggeringPolicy. My understanding is that when the log rolls due to the TimeBasedTriggeringPolicy, the counter associated with the SizeBasedTriggeringPolicy should reset to 1, but this isn't happening. It just keeps incrementing from where it left off. Here is my config file. Any ideas? Thanks in advance.
Beta Was this translation helpful? Give feedback.
All reactions