snicoll opened a new issue, #4001:
URL: https://github.com/apache/logging-log4j2/issues/4001

   ## Description
   
   Apologizes for the lack of details but @ppkarwasz mentioned it could 
reproduce the problem on their end.
   
   I am configuring a `SizeBasedTriggeringPolicy` on a Spring Boot application 
and rolling fails as follows:
   
   ```
   2025-12-12T14:23:34.834545Z scheduling-1 ERROR An exception occurred 
processing Appender File
   java.lang.IndexOutOfBoundsException: No group 1
        at java.base/java.util.regex.Matcher.checkGroup(Matcher.java:1845)
        at java.base/java.util.regex.Matcher.group(Matcher.java:686)
        at 
org.apache.logging.log4j.core.appender.rolling.AbstractRolloverStrategy.getEligibleFiles(AbstractRolloverStrategy.java:144)
        at 
org.apache.logging.log4j.core.appender.rolling.AbstractRolloverStrategy.getEligibleFiles(AbstractRolloverStrategy.java:93)
        at 
org.apache.logging.log4j.core.appender.rolling.AbstractRolloverStrategy.getEligibleFiles(AbstractRolloverStrategy.java:85)
        at 
org.apache.logging.log4j.core.appender.rolling.DefaultRolloverStrategy.purgeAscending(DefaultRolloverStrategy.java:447)
        at 
org.apache.logging.log4j.core.appender.rolling.DefaultRolloverStrategy.purge(DefaultRolloverStrategy.java:431)
        at 
org.apache.logging.log4j.core.appender.rolling.DefaultRolloverStrategy.rollover(DefaultRolloverStrategy.java:571)
        at 
org.apache.logging.log4j.core.appender.rolling.RollingFileManager.rollover(RollingFileManager.java:619)
        at 
org.apache.logging.log4j.core.appender.rolling.RollingFileManager.rollover(RollingFileManager.java:507)
        at 
org.apache.logging.log4j.core.appender.rolling.RollingFileManager.checkRollover(RollingFileManager.java:418)
        at 
org.apache.logging.log4j.core.appender.RollingFileAppender.append(RollingFileAppender.java:336)
        at 
org.apache.logging.log4j.core.config.AppenderControl.tryCallAppender(AppenderControl.java:160)
        at 
org.apache.logging.log4j.core.config.AppenderControl.callAppender0(AppenderControl.java:133)
        at 
org.apache.logging.log4j.core.config.AppenderControl.callAppenderPreventRecursion(AppenderControl.java:124)
        at 
org.apache.logging.log4j.core.config.AppenderControl.callAppender(AppenderControl.java:88)
        at 
org.apache.logging.log4j.core.config.LoggerConfig.callAppenders(LoggerConfig.java:711)
        at 
org.apache.logging.log4j.core.config.LoggerConfig.processLogEvent(LoggerConfig.java:669)
        at 
org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:645)
        at 
org.apache.logging.log4j.core.config.LoggerConfig.logParent(LoggerConfig.java:702)
        at 
org.apache.logging.log4j.core.config.LoggerConfig.processLogEvent(LoggerConfig.java:671)
        at 
org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:645)
        at 
org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:589)
        at 
org.apache.logging.log4j.core.config.DefaultReliabilityStrategy.log(DefaultReliabilityStrategy.java:73)
        at org.apache.logging.log4j.core.Logger.log(Logger.java:187)
        at 
org.apache.logging.log4j.spi.AbstractLogger.tryLogMessage(AbstractLogger.java:2970)
        at 
org.apache.logging.log4j.spi.AbstractLogger.logMessageTrackRecursion(AbstractLogger.java:2922)
        at 
org.apache.logging.log4j.spi.AbstractLogger.logMessageSafely(AbstractLogger.java:2904)
        at 
org.apache.logging.log4j.spi.AbstractLogger.logMessage(AbstractLogger.java:2653)
        at 
org.apache.logging.log4j.spi.AbstractLogger.logIfEnabled(AbstractLogger.java:2393)
        at org.apache.logging.slf4j.Log4jLogger.debug(Log4jLogger.java:113)
   ```
   
   When this happens logs to file stop.
   
   ## Configuration
   
   Log4J 2.25.2, MacOS, JDK 25
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to