When two or more rolling file appenders are sharing the same logfile then logging is working not as expected. Logging files will be rolled at unexpected size and logging will still be done on artifact files *.1, *.2 a.s.o.
The problem is that all appenders are rolling independed of each other. When the first has done the rolling, all others are operation on an obsolete log file / fd. A possible solution would be to let other appenders reload their fd after each rollover.
can you please attach a small example with two rolling file appenders on the same logfile?
Here the configuration of two different rolling appenders logging into the same file (...summ.log) even if the size setting is equal.
appender FWFMO.FWCNF basic rolling /opt/appl/data/log/summ.log 5000000 7
priority FWFMO.FWCNF INFO
appender FWFMO.FWPWR basic rolling /opt/appl/data/log/summ.log 5000000 7
priority FWFMO.FWPWR DEBUG
Scenario: the firts appender will rollover when the size threshold is crossed. As result, the second appenders fd will be pointing to summ.log.1 (!). Then it will write there a new log message and encounter the size threshold over limit. Then it will rollover even when the summ.log is not full, a.s.o.
Also please look at RollingFileAppender::rollover().
Two file appenders are not really supposed to share a single output file.
If you want to log from different places/threads, that is better achieved with sharing a single appender (and optionally using NDC feature).