Home → General Feedback →

query on couple of log messages

• Edit

carballo

02 Jul, 2013 04:07 PM

Hello

I came across a couple of messages in the logs that I'd like to ask you about.

1- How concern should I be about?:

2013-06-09 05:07:02,315 WARN [CascadeEhCacheManagerFactoryBean] : Could not load properties for Ehcache configuration. Checking if ehcache.xml has been provided. Error message: /home/cascade/cscurrent/tomcat/conf/ehcache.properties (No such file or directory)

2- The second one relates to slf4j:

SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.

I followed the link and did get further details:

This error is reported when the org.slf4j.impl.StaticLoggerBinder class could not be loaded into memory. This happens when no appropriate SLF4J binding could be found on the class path. Placing one (and only one) of slf4j-nop.jar, slf4j-simple.jar, slf4j-log4j12.jar, slf4j-jdk14.jar or logback-classic.jar on the class path should solve the problem. since 1.6.0 As of SLF4J version 1.6, in the absence of a binding, SLF4J will default to a no-operation (NOP) logger implementation. (http://www.slf4j.org/codes.html#StaticLoggerBinder)

Should I follow their recommendation of placing "one (and only one) of slf4j-nop.jar, slf4j-simple.jar, slf4j-log4j12.jar, slf4j-jdk14.jar or logback-classic.jar on the class path."?

Thanks

Erick Carballo
Indiana University

1. Support Staff 1 Posted by Tim on 02 Jul, 2013 06:08 PM

   

   Hi Erick,

   Regarding this message:

   2013-06-09 05:07:02,315 WARN [CascadeEhCacheManagerFactoryBean] : Could not load properties for Ehcache configuration. Checking if ehcache.xml has been provided. Error message: /home/cascade/cscurrent/tomcat/conf/ehcache.properties (No such file or directory)

   That seems to indicate that the O/S account running the Cascade Server process doesn't have access to that particular file. Can you check the access rights on the server to see what those file permissions are (as well as the other files under the tomcat/conf folder?

   For this message:

   SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.

   I remembered that another client mentioned this behavior on this public discussion. Can you watch that discussion? I'll ask my developers to chime in again and we'll see if we can track down where things are going wrong.

   Thanks!

   • Edit

2. Ryan Griffith closed this discussion on 31 Dec, 2013 02:18 PM.