Stirling-PDF/app/core/src/main/resources/logback.xml

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
	<define name="LOG_PATH" class="stirling.software.SPDF.config.LogbackPropertyLoader" />

    <!-- Console Appender -->
    <appender name="CONSOLE" class="ch.qos.logback.core.ConsoleAppender">
        <encoder>
            <pattern>%d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n</pattern>
        </encoder>
    </appender>

    <!-- Rolling File Appender for Auth Logs -->
    <appender name="AUTHLOG" class="ch.qos.logback.core.rolling.RollingFileAppender">
        <file>${LOG_PATH}/invalid-auths.log</file>
        <encoder>
            <pattern>%d %p %c{1} [%thread] %m%n</pattern>
        </encoder>
        <!-- SizeAndTime, not Time alone: the size trigger is what stops a
             runaway logger filling the disk (see GENERAL appender note).
             Archives are gzipped, so 64 MB of them holds far more than a
             day. Worst case on disk is one 100 MB live file plus the cap. -->
        <rollingPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedRollingPolicy">
            <fileNamePattern>${LOG_PATH}/auth-%d{yyyy-MM-dd}.%i.log.gz</fileNamePattern>
            <maxFileSize>100MB</maxFileSize>
            <maxHistory>7</maxHistory>
            <totalSizeCap>64MB</totalSizeCap>
        </rollingPolicy>
    </appender>

    <!-- Rolling File Appender for General Logs

         Why SizeAndTimeBased + totalSizeCap: a previous build of the v2 PDF
         text editor's reverse-CMap probe loop triggered PDSimpleFont to emit
         one "No Unicode mapping for .notdef" WARN per probed charcode per
         font per request. With TimeBasedRollingPolicy alone there was no
         size ceiling; info.log grew to 1.4 GB in a single day before the JVM
         choked. The class-level silencer fixes the specific offender, but
         this size cap is the defence-in-depth: any future logger that
         floods unexpectedly will roll + auto-delete instead of starving
         disk + Jetty threads. -->
    <appender name="GENERAL" class="ch.qos.logback.core.rolling.RollingFileAppender">
        <file>${LOG_PATH}/info.log</file>
        <encoder>
            <pattern>%d %p %c{1} [%thread] %m%n</pattern>
        </encoder>
        <rollingPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedRollingPolicy">
            <fileNamePattern>${LOG_PATH}/info-%d{yyyy-MM-dd}.%i.log.gz</fileNamePattern>
            <maxFileSize>100MB</maxFileSize>
            <maxHistory>7</maxHistory>
            <totalSizeCap>256MB</totalSizeCap>
        </rollingPolicy>
    </appender>

    <!-- Suppress PDFBox PDSimpleFont's per-charcode .notdef WARN.

         Required by the v2 PDF text editor's `buildReverseUnicodeMap`
         which DELIBERATELY iterates every charcode in 0..0xFFFF to
         discover the encoding-to-Unicode map of an embedded subset
         font. For any subset font ~99% of those probes hit .notdef,
         and the default WARN level for those misses turned info.log
         into a 1.4 GB monster overnight.

         This declarative logback entry is the SOLE mechanism: it is
         visible to ops and revertable via configuration. An earlier
         build also mutated this logger's level from a static block in
         PdfTextEditorCharcodeController, which silenced the same
         warnings JVM-wide with no trace in any config file - that
         static block has been removed in favour of this entry. -->
    <logger name="org.apache.pdfbox.pdmodel.font.PDSimpleFont"
            level="ERROR" additivity="false">
        <appender-ref ref="CONSOLE"/>
        <appender-ref ref="GENERAL"/>
    </logger>

    <!-- Root Logger -->
    <root level="INFO">
        <appender-ref ref="CONSOLE"/>
        <appender-ref ref="GENERAL"/>
    </root>

    <!-- Specific Logger -->
    <logger name="stirling.software.proprietary.security.CustomAuthenticationFailureHandler"
            level="ERROR" additivity="false">
        <appender-ref ref="CONSOLE"/>
        <appender-ref ref="AUTHLOG"/>
    </logger>
</configuration>