Thx for your feedback! Yeah, your test case works fine. But my setup is a little different, since I'm running logback in a servlet application scenario. Another difference is that I'm using an <include> directive to solve some difficulties with the os specific path separators, like this:
<?xml version="1.0" encoding="UTF-8"?>
<configuration scan="true">
<if condition='property("os.name").toLowerCase().contains("win")'>
<then>
<include file="${xom.home:-C:/default/path}/logback-config.xml"/>
</then>
<else>
<include file="${xom.home:-/var/default/path}/logback-config.xml"/>
</else>
</if>
</configuration>
Perhaps there have been changes in the initialization process which might be related to the problem? In previous versions the setAppenderFactory method has been called in ch.qos.logback.classic.sift.SiftAction.end() - which obviously works differently in current versions. Yet I have not been able to track the problem further down, which at last leads to the situation described above, where the unset AppenderFactory leads to the "Aborting" scenario... |