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!/log4j.properties was used. So I also added "-Dlog4j.configuration=file:///apps/tomcat/webapps/cocoon/WEB-INF/log4j. xml" with the following settings <log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/";> <appender name="COCOON_DEFAULT" class="org.apache.log4j.FileAppender"> <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} - %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 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, Alexander
