Error: SLF4J: Failed to load class StaticLoggerBinder during Reporter Server startup

Products

• Automic Dollar Universe

Issue/Introduction

After upgrading to Reporter 6.10.121, the startup console or startup.log may display  verbose Ehcache DEBUG messages. These messages appear immediately after the "Reporter server is launched in background" banner.

===============================================

[Thread-1] DEBUG net.sf.ehcache.CacheManager - Creating new CacheManager with default config
[Thread-1] DEBUG net.sf.ehcache.CacheManager - Configuring ehcache from classpath.
[Thread-1] WARN  net.sf.ehcache.config.ConfigurationFactory - No configuration found. Configuring ehcache from ehcache-failsafe.xml  found in the classpath: jar:file:/opt/AUTOMIC/Reporter/btama-aai/exec/ehcache.jar!/ehcache-failsafe.xml
[Thread-1] DEBUG net.sf.ehcache.config.ConfigurationFactory - Configuring ehcache from URL: jar:file:/opt/AUTOMIC/Reporter/btama-aai/exec/ehcache.jar!/ehcache-failsafe.xml
[Thread-1] DEBUG net.sf.ehcache.config.ConfigurationFactory - Configuring ehcache from InputStream
[Thread-1] DEBUG net.sf.ehcache.config.DiskStoreConfiguration - Disk Store Path: /tmp
[Thread-1] DEBUG net.sf.ehcache.config.ConfigurationHelper - No CacheManagerEventListenerFactory class specified. Skipping...
[Thread-1] DEBUG net.sf.ehcache.config.ConfigurationHelper - No CachePeerListenerFactoryConfiguration specified. Not configuring a CacheManagerPeerListener.
[Thread-1] DEBUG net.sf.ehcache.config.ConfigurationHelper - No CachePeerProviderFactoryConfiguration specified. Not configuring a CacheManagerPeerProvider.
[Thread-1] DEBUG net.sf.ehcache.config.ConfigurationHelper - No BootstrapCacheLoaderFactory class specified. Skipping...

===============================================

Environment

• Dollar Universe Reporter 6.10.121
• Linux

Cause

Reporter 6.10.121 migrated to Log4j2 and upgraded third-party libraries (Hibernate, Spring). The unistartrep script on Linux captures the background Java process's standard output and displays it to the console.

This message can appear when the Reporter server is stopped and the unistartrep command is executed immediately. It is possible that the Reporter process was not fully stopped at the time of execution. This represents a timing/synchronization issue between the unistoprep and unistartrep commands. These messages are internal library initialization or shutdown chatter and do not have any impact on the functionalities of Reporter.

Resolution

 These messages are benign and can be ignored. 

To suppress verbose Ehcache DEBUG chatter for a cleaner console output:

1. Navigate to the mgr directory of the Reporter installation.
2. Back up the log4j2.xml file.
3. Edit log4j2.xml and add the following logger category before the <Root> section:

     .
     .
     .
     <Logger name="net.sf.ehcache" level="ERROR" additivity="false" includeLocation="false">
            <AppenderRef ref="ADDITIONAL_FRAMEWORKS_SIZE_LIMITER" />
      </Logger>

        <Root level="DEBUG">
            <AppenderRef ref="STDOUT"/>
        </Root>

4. Restart the Reporter server.