ConsoleAppender ignored in logback-access.xml

[gomil]

While upgrading logback-core from 1.5.22 to 1.5.23, we encountered errors related to our configuration in logback-access.xml.

INFO in ch.qos.logback.access.tomcat.LogbackValve[null] - Could NOT find configuration file [/private/var/folders/p0/fgdty5yn6d3glgfn0qxv9cm80000gq/T/tomcat.8080.14039878947770433632/logback-access.xml] using property "catalina.base"
INFO in ch.qos.logback.access.tomcat.LogbackValve[null] - Could NOT find configuration file [/private/var/folders/p0/fgdty5yn6d3glgfn0qxv9cm80000gq/T/tomcat.8080.14039878947770433632/logback-access.xml] using property "catalina.home"
INFO in ch.qos.logback.access.tomcat.LogbackValve[null] - Found [logback-access.xml] as a resource.
WARN in ch.qos.logback.core.model.processor.AppenderModelHandler - Appender named [logstash] not referenced. Skipping further processing.
ERROR in ch.qos.logback.core.model.processor.AppenderRefModelHandler - Failed to find appender named [logstash]
INFO in ch.qos.logback.core.model.processor.DefaultProcessor@71fb8301 - End of configuration.
INFO in ch.qos.logback.access.common.joran.JoranConfigurator@7cdfa824 - Registering current configuration as safe fallback point
INFO in ch.qos.logback.access.tomcat.LogbackValve[null] - Done configuring

It appears that the configured ConsoleAppender is no longer recognized. After reviewing the release notes, we identified this commit as the likely cause. The logic for binding loggers to appenders seems to have moved from a global location to a more specific one (FileAppender), resulting in the ConsoleAppender no longer being picked up.

This is our logback-access.xml

<configuration debug="true">

  <appender name="logstash" class="ch.qos.logback.core.ConsoleAppender"/>

  <appender-ref ref="logstash"/>

</configuration>

The non-accesslog configuration for ConsoleAppender still appears to work.

Environment

• spring-boot:3.5.9
• amazoncorretto:21.0.9

If you need any further information to reproduce the issue, please let me know.

Best regards, Andy

[ceki]

@gomil Thank you for this timely report. Can you please try logback-access version 2.0.8 released very recently?

[gomil]

@ceki

Your reference to logback-access 2.0.8 made me realize there was an error in our configuration.
When updating to logback 1.5.23, we overlooked updating logback-access accordingly (used still 2.0.6).
I was able to confirm that the error no longer occurs with logback 1.5.24 and logback-access 2.0.8.

Thank you very much and best regards
Andy