Issue Summary

When starting up an unmodified Confluence instance,  the following message can be seen in the Catalina log:

... 
SLF4J(E): A service provider failed to instantiate:
org.slf4j.spi.SLF4JServiceProvider: Provider org.apache.logging.slf4j.SLF4JServiceProvider not found
SLF4J(W): No SLF4J providers were found.
SLF4J(W): Defaulting to no-operation (NOP) logger implementation
SLF4J(W): See https://www.slf4j.org/codes.html#noProviders for further details.... 

This is similar to the JSDSERVER-16004 bug for Jira Service Management.

This is reproducible on Data Center: Yes

Steps to Reproduce

1. Start a Confluence 9.x instance
2. Check <install_path>/logs/catalina.out

Expected Results

No warnings generated.

Actual Results

The below exception is thrown in the catalina.out file:

SLF4J(E): A service provider failed to instantiate:
org.slf4j.spi.SLF4JServiceProvider: Provider org.apache.logging.slf4j.SLF4JServiceProvider not found
SLF4J(W): No SLF4J providers were found.
SLF4J(W): Defaulting to no-operation (NOP) logger implementation
SLF4J(W): See https://www.slf4j.org/codes.html#noProviders for further details. 

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available