Why are Conluence's log4j.properties changes being kept after roll-over?

[Gaven Ray]

I am working with Confluence in a Docker container and trying to make changes to log4j.properties. 

The changes take on restart of the container but when the log rolls over at a smalller size than it states in the file. The other changes I made revert. 

atlassian-confluence-dev.log is correct based on the file. Once it hits 21M it rolls over and goes to atlassian-confluence.log.

log4j.appender.confluencelog.LogFileName=atlassian-confluence-dev.log
log4j.appender.confluencelog.Threshold=DEBUG
log4j.appender.confluencelog.MaxFileSize=300MB
log4j.appender.confluencelog.MaxBackupIndex=5
log4j.appender.confluencelog.layout=com.atlassian.confluence.util.PatternLayoutWithContext
log4j.appender.confluencelog.layout.ConversionPattern=%d %p [%t] [%c{4}] %M %m%n

I have commented out:

# Appender that burst limits log messages
#log4j.appender.burstFilterAppender=com.atlassian.confluence.logging.ConfluenceHomeLogAppender
#log4j.appender.burstFilterAppender.Threshold=ALL
#log4j.appender.burstFilterAppender.layout=com.atlassian.confluence.util.PatternLayoutWithContext
#log4j.appender.burstFilterAppender.layout.ConversionPattern=%d %p [%t] [%c{4}] %M %m%n
#log4j.appender.burstFilterAppender.filter.1=com.atlassian.confluence.impl.logging.filter.BurstFilter
#log4j.appender.burstFilterAppender.filter.1.Level=WARN
#log4j.appender.burstFilterAppender.filter.1.Rate=0.5
#log4j.appender.burstFilterAppender.filter.1.MaxBurst=5

#log4j.logger.com.atlassian.analytics.client.listener.ProductEventListener=WARN, burstFilterAppender
#log4j.additivity.com.atlassian.analytics.client.listener.ProductEventListener=false

based on https://jira.atlassian.com/browse/CONFSERVER-91703
That also does not seem to help. 

[Brant Schroeder]

@Gaven Ray Are you running a multi-node instance?  If yes are you applying the change to each instance?

[Gaven Ray]

No, this is a single instance system.