cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lochschmied, Alexander" <>
Subject Re: ehcache blows up catalina.out
Date Thu, 08 Jul 2010 10:48:26 GMT
Hi Jeroen and All,


Thanks for this great suggestion, I added "-Dlog4j.debug=true" directive
and catalina.out revealed that
cocoon/WEB-INF/lib/bsf-2.4.0.jar!/ was used.

So I also added
xml" with the following settings


<log4j:configuration xmlns:log4j="">

    <appender name="COCOON_DEFAULT"

        <param name="File"
value="${context-root}/WEB-INF/logs/log4j.log" />

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

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

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




      <priority value="fatal" />

      <appender-ref ref="COCOON_DEFAULT" />


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

      <level value="info" />

      <appender-ref ref="COCOON_DEFAULT" />




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


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


24100 [http-8080-7] DEBUG net.sf.ehcache.Cache  - cocoon-ehcache-1 cache
- Miss


Do you have an idea what might still go wrong?


Best regards,


View raw message