tag:help-archives.hannonhill.com,2010-02-09:/discussions/general-feedback/10477-query-on-couple-of-log-messagesCascade CMS: Discussion 2014-03-25T20:54:34Ztag:help-archives.hannonhill.com,2010-02-09:Comment/275897172013-07-02T16:07:08Z2013-07-02T16:07:08Zquery on couple of log messages<div><p>Hello</p>
<p>I came across a couple of messages in the logs that I'd like to
ask you about.</p>
<p>1- How concern should I be about?:</p>
<blockquote>
<p>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)</p>
</blockquote>
<p>2- The second one relates to slf4j:</p>
<blockquote>
<p>SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See <a href=
"http://www.slf4j.org/codes.html#StaticLoggerBinder">http://www.slf4j.org/codes.html#StaticLoggerBinder</a>
for further details.</p>
</blockquote>
<p>I followed the link and did get further details:</p>
<blockquote>
<p>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.
(<a href=
"http://www.slf4j.org/codes.html#StaticLoggerBinder">http://www.slf4j.org/codes.html#StaticLoggerBinder</a>)</p>
</blockquote>
<p>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."?</p>
<p>Thanks</p>
<p>Erick Carballo<br>
Indiana University</p></div>carballotag:help-archives.hannonhill.com,2010-02-09:Comment/275897172013-07-02T18:08:31Z2013-07-02T18:08:31Zquery on couple of log messages<div><p>Hi Erick,</p>
<p>Regarding this message:</p>
<blockquote>
<p>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)</p>
</blockquote>
<p>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
<em>tomcat/conf</em> folder?</p>
<p>For this message:</p>
<blockquote>
<p>SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See <a href=
"http://www.slf4j.org/codes.html#StaticLoggerBinder">http://www.slf4j.org/codes.html#StaticLoggerBinder</a>
for further details.</p>
</blockquote>
<p>I remembered that another client mentioned this behavior on
<a href=
"http://help.hannonhill.com/discussions/installation/1219-custom-install-questions">
this public discussion</a>. 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.</p>
<p>Thanks!</p></div>Tim