Springboot - not replace spring propreties in log4j.xml about logging-log4j2 HOT 3 CLOSED

@ppkarwasz I have the same problem since I upgraded from 2.17.2 to 2.19 (Spring boot 2.3.9)
I don't need two log4j files or arbiters to make it work in 2.17.2

But since 2.18 it stopped working because of the new way to load LoggingSystemFactory (spring.factories)
I still don't understand why spring.factories are not loaded

EDIT : It don't work because LoggingSystemFactory does not exist before Spring 2.4, the documentation mention that the lib require Spring boot 2.0.3 or 2.1.1, which is outdated since Log4J 2.18

from logging-log4j2.

@schotten,

Logging in a Spring Boot application is configured at least twice:

• when the SpringApplication class is loaded (that is what you see in your stacktrace). This process is described in automatic configuration and does not have access to Spring's environment (that didn't start yet),
• after the ApplicationEnvironmentPreparedEvent is fired (cf. lifecycle of a Spring Boot application). This process is specific to Spring Boot, has access to Spring's environment and uses the log4j2-spring.xml file (falling back on log4j2.xml if such a file does not exist).

If you want to use Spring's enviroment to configure your logging system you have to options:

1. Create two files: log4j2.xml and log4j2-spring.xml. The first one will be used during the bootstrap phase of your application and can not use Spring's environment. The second one will be used, when your application is up and running.
2. Stick to a single configuration file and use arbiters to provide multiple versions of your "solver-service" appender:

<Select>
    <SpringProfile name="dev">
        <File name="solver-service" fileName="${spring:log4j.solver.service.path}" append="false">
            <EcsLayout serviceName="${spring:log4j.solver.service.name}" serviceVersion="${spring:log4j.solver.service.version}"  serviceEnvironment="${spring:log4j.solver.service.enviroment}"/>
        </File>
    </SpringProfile>
    <DefaultArbiter>
        <Null name="solver-service"/>
    </DefaultArbiter>
</Select>

from logging-log4j2.

I am closing this for lack of activity. I think that:

• my previous comment solves @schotten's problem,
• @SebHeuze's problem was discussed in #1652.

Fill free to reopen the issue.

from logging-log4j2.