Details
-
Bug
-
Resolution: Duplicate
-
Major
-
1.1.7
Description
Application upgraded from logback 1.1.2 to 1.1.7 after that facing the following issue.
Ideally the below scenario never produces same file name but it's throwing the below error. Logback stops logging instead of recovering from the error.
<property name="logback.logdir" value="logs/appgensrv/" /> <property name="logback.backupdir" value="logs/appgensrv/tmp/" /> <property name="logback.rollingPattern" value="%d{yyyy-MM-dd_HH}" /> <appender name="TRACE" class="ch.qos.logback.classic.sift.SiftingAppender"> <discriminator> <key>siftdomain</key> <defaultValue>unknown</defaultValue> </discriminator> <sift> <appender name="FILETD-${siftdomain}" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>${logback.logdir}/${siftdomain}_trace.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>${logback.backupdir}/${siftdomain}_trace.log.${logback.rollingPattern}</fileNamePattern> </rollingPolicy> <encoder> <pattern>${logback.fullPattern}</pattern> </encoder> </appender> </sift> </appender>
ERROR in ch.qos.logback.core.rolling.RollingFileAppender[FILETD-AGR] - 'FileNamePattern' option has the same value "logs/appgensrv/tmp//AGR_trace.log.%d
{yyyy-MM-dd_HH}" as that given for appender [FILETD-AGR] defined earlier.
ERROR in ch.qos.logback.core.rolling.RollingFileAppender[FILETD-AGR] - Collisions detected with FileAppender/RollingAppender instances defined earlier. Aborting.
ERROR in ch.qos.logback.core.rolling.RollingFileAppender[FILETD-AGR] - For more information, please visit http://logback.qos.ch/codes.html#earlier_fa_collision
Attachments
Issue Links
- depends on
-
LOGBACK-1167 Filename Patterns remain in context collision map following stop
- Resolved