The following configuration file: https://git.magnolia-cms.com/projects/ADDON/repos/ecommerce/browse/magnolia-ecommerce-commercetools-connector/src/main/resources/log4j2.xml

Is probably the reason we have 50MB log files in any project that uses the commercetools-connector such as addon-tests: https://jenkins.magnolia-cms.com/job/internal/job/addon-tests/job/master/lastSuccessfulBuild/artifact/catalina-2d034ef9eca1.log

The reason for this is seen at the following reference: org.apache.logging.log4j.core.Logger.PrivateConfig#PrivateConfig(org.apache.logging.log4j.core.config.Configuration, org.apache.logging.log4j.core.Logger)

With a breakpoint there, one can see that DEBUG/TRACE logging coming from org.apache.commons is visible right after the log4j2.xml file from ecommerce is parsed.

This could be solved for instance by setting the level to INFO rather than ALL (done by Maxime). Then it is a matter of verifying that the extreme logging is gone from the addon-packs webapp, and making sure the ecommerce connector also doesn't output debug information at every client request.