OutOfMemory exception on tomcat / Change logging bridge dependency.

[fxprunayre]

Tomcat (left) and Jetty (right) during indexing phase:

A memory leak is observed on Tomcat related to logging.

slf4j usage:

~/webapps/geonetwork/WEB-INF/lib$ find . -name "*slf4j*.jar"
./jcl-over-slf4j-1.7.5.jar
./log4j-slf4j18-impl-2.17.2.jar
./slf4j-api-1.7.36.jar
./jclouds-slf4j-2.2.1.jar
./log4j-slf4j-impl-2.17.2.jar

slf4j-api-1.7.36 is used and should not contain memory leak observed on slf4j before 1.7.21 (https://www.slf4j.org/news.html#1.7.21).

We were using log4j-slf4j18-impl which is not the version recommended to use with version 1.7.x.

* log4j-slf4j-impl should be used with SLF4J 1.7.x releases or older.
* As of release 2.19.0 the log4j-slf4j18-impl module targetting the unreleased SLF4J 1.8.x series has been removed.

Changing the dependency version of the bridge looks to fix the memory leak observed on Tomcat.

Thanks to @cmangeat and @juanluisrp for giving ideas.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication