Check SLF4J Bindings:

• Since you've already tried different SLF4J configurations like slf4j-nop and slf4j-simple, double-check that there are no other conflicting SLF4J bindings in your classpath. Sometimes, having multiple versions of SLF4J-related libraries can lead to unexpected behavior. Remove any unnecessary or duplicate SLF4J jars from your application's dependencies. Ensure that the SLF4JBridgeHandler is configured correctly. The error stack shows that it might be involved in the recursive calls. Review how you are setting up the bridge between Java's java.util.logging and SLF4J.

Review Logging Levels and Configuration Files:

• Although you've tried switching logging levels, make sure that all logging configuration files (such as log4j.properties or logback.xml if applicable) are consistent and not misconfigured. Incorrect logging level settings or overly verbose logging configurations can sometimes trigger issues like this. Try to simplify the logging configuration to its bare minimum and gradually add back features to see if the problem persists.