ContentCreator + FirstSpirit Integration (ab 2022.5): Problem log4j slf4j

Author: alexitelligence
Publication Date: 11/9/2022 12:56

Hallo zusammen,

ich habe schon ein Support-Ticket laufen, aber dachte ich probiere es mal gleichzeitig hier.

Wir kriegen ab Version 2022.5 den ContentCreator nicht mehr mit dem FS-Integration-Modul zum starten:

04-Nov-2022 11:12:14.841 INFO [http-nio-8080-exec-19] org.apache.catalina.startup.HostConfig.deployWAR Deploying web application archive [/opt/firstspirit5/web/fs5webedit_14.war]
04-Nov-2022 11:12:20.116 INFO [http-nio-8080-exec-19] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping u
nneeded JARs during scanning can improve startup time and JSP compilation time.
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/opt/firstspirit5/web/fs5webedit_14/WEB-INF/lib/log4j-slf4j-impl-2.17.2.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/opt/firstspirit5/web/fs5webedit_14/WEB-INF/lib/logback-classic-1.2.11.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.apache.logging.slf4j.Log4jLoggerFactory]
04-Nov-2022 11:12:20.553 SEVERE [http-nio-8080-exec-19] org.apache.catalina.core.ContainerBase.addChildInternal ContainerBase.addChild: start:
        org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/fs5webedit_14]]
...
Caused by: org.apache.logging.log4j.LoggingException: log4j-slf4j-impl cannot be present with log4j-to-slf4j
...
04-Nov-2022 11:12:20.554 SEVERE [http-nio-8080-exec-19] org.apache.catalina.startup.HostConfig.deployWAR Error deploying web application archive [/opt/firstspirit5/web/fs5webedit_14.war]
        java.lang.IllegalStateException: Error starting child
...
Caused by: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/fs5webedit_14]]
                at org.apache.catalina.util.LifecycleBase.handleSubClassException(LifecycleBase.java:440)
                at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:198)
                at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:753)
                ... 46 more
        Caused by: org.apache.logging.log4j.LoggingException: log4j-slf4j-impl cannot be present with log4j-to-slf4j

Es handelt sich um das Mithras Energy Demo-Project. Im ContentCreator ist nur FS Integration installiert, sonst keine andere Web-Anwendung.

Der ContentCreator bringt von sich aus

<resource name="org.apache.logging.log4j:log4j-to-slf4j" version="2.17.2" minVersion="2.17.2">lib/log4j-to-slf4j-2.17.2.jar</resource>

mit.

FS Integration bringt:

<resource name="org.apache.logging.log4j:log4j-slf4j-impl" version="2.17.2" minVersion="2.17.2" maxVersion="2.17.99">lib/log4j-slf4j-impl-2.17.2.jar</resource>

mit.

Diese beiden Jars landen im Tomcat und der ContentCreator kann nicht starten.

Hat sonst jemand das gleiche Problem? Oder andersrum gefragt: hat jemand FS >= 2022.5 mit ContentCreator und FS Integration erfolgreich am laufen?

Danke und viele Grüße

Alex