cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lochschmied, Alexander" <Alexander.Lochschm...@vishay.com>
Subject ehcache blows up catalina.out
Date Tue, 13 Jul 2010 10:49:20 GMT
Hi everybody!

 

I first got confused about ehcache using slf4j, but after decompiling ehachace from our Cocoon
2.1.11 (Tomcat is 6.0.20), I noticed commons logging was used back then. 

 

The problem is (still): Our tomcat/logs/catalina.out logs too many DEBUG messages generated
in ehcache, like

 

85765 [http-8080-5] DEBUG net.sf.ehcache.Cache  - cocoon-ehcache-1 cache - Miss

85765 [http-8080-5] DEBUG net.sf.ehcache.Cache  - cocoon-ehcache-1 cache - Miss

85946 [http-8080-5] DEBUG net.sf.ehcache.store.MemoryStore  - cocoon-ehcache-1Cache: spool
to disk done for: PK_G-file-file:///.../nothing.xml_T-xslt-file:///.../press-query.xsl;id=xyz

 

This causes huge catalina.out, around 5 GB per day, so we need to restart tomcat and purge
the log file.

 

I tried a lot of config settings, most promising was adding "-Dlog4j.debug=true" directive
(to JAVA call starting tomcat). catalina.out revealed that cocoon/WEB-INF/lib/bsf-2.4.0.jar!/log4j.properties
was used!

 

So I also added "-Dlog4j.configuration=file:///tomcat/webapps/cocoon/WEB-INF/log4j.xml" with
the following settings

 

<log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/ <http://jakarta.apache.org/log4j/>
">

    <appender name="COCOON_DEFAULT" class="org.apache.log4j.FileAppender">

        <param name="File"   value="/tomcat/webapps/cocoon/WEB-INF/logs/log4j.log" />

        <param name="Append" value="false" />

        <layout class="org.apache.log4j.PatternLayout">

            <param name="ConversionPattern" value="%t %-5p %c{2} - %m%n"/>

        </layout>

    </appender>

    <root>

      <priority value="fatal" />

      <appender-ref ref="COCOON_DEFAULT" />

    </root>

    <logger name="net.sf.ehcache">

      <level value="info" />

      <appender-ref ref="COCOON_DEFAULT" />

    </logger>

</log4j:configuration>

 

And it seems to be actually used as catalina.out now prints

 

log4j: Setting [net.sf.ehcache] additivity to [true].

log4j: Level value for net.sf.ehcache is  [info].

log4j: net.sf.ehcache level set to INFO

log4j: Adding appender named [COCOON_DEFAULT] to category [net.sf.ehcache].

 

But as you already guessed, I still get tons of ehcahce debug messages in catalina.out, like

 

Do you have an idea what might still go wrong?

What could cause these DEBUG messages to still go to stdout (or stderr)?

 

Thanks in advance,

Alexander

 

Alexander Lochschmied 

Web Programmer - Internet and Commerce 

IT Global Web Services 

Information Technology

Phone:    +49 92 8771 2682

Fax       +49 92 8771 2545

Website:  www.vishay.com <http://www.vishay.com/> 

  

Vishay Electronic GmbH

Geheimrat-Rosenthal-Str. 100 

D-95100 Selb 

Amtsgericht/County Court Hof HRB 2894, 

Geschäftsführer/Managing Directors: Sieglinde Janker-Buecherl, Arnold Rohr

 


Mime
View raw message