cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joose Vettenranta <>
Subject cocoon stalls/freezes - big problem
Date Fri, 19 Mar 2004 12:32:04 GMT

I've had problems with freezing/stalling from time to time in very  
oddly places and times. Sometimes it's fop which hangs but sometimes  
it's just some sub sitemap like today. Restarting tomcat helps. Same  
stalling happened with tomcat 4.1.21 and cocoon 2.0.3...

If I have to access XSP-files so those are compiled many times,  
something might stall/freeze/jam after that.

I would like to know why it freezes (is the problem tomcat or cocoon?).  
Most likely no one is not able to say for sure, but I would like to  
know some tips or instructions how to track that problem, like when it  
stalls, then what?
And how to fix this annoying problem?


Base system: Redhat 9

Apache 2.0.something acting as proxy. (this is not a problem, because  
direct access to tomcat is not working when something is stalled)

Tomcat 4.1.29
Cocoon 2.1.3
Java SDK = 1.4.2_02

Log file is sometimes registering calls but sometimes not. It just  
stalls somewhere. Memory is not short.

tomcat is run using following command line:

according to log files, there is lot's of free memery.

     <Engine name="Standalone" defaultHost="localhost" debug="8">
       <Host name="localhost" debug="8"  
        unpackWARs="true" autoDeploy="true">
         <Logger className="org.apache.catalina.logger.FileLogger"
                  directory="logs" prefix="localhost_log." suffix=".txt"
         <Context path="" docBase="cocoon" debug="8" />

in sitemap.xmap (top-level) I have:

     <map:transformer logger="sitemap.transformer.xslt" name="xslt"  
pool-grow="2" pool-max="256" pool-min="8"  

     <map:serializer logger="sitemap.serializer.fo2pdf"  
mime-type="application/pdf" name="fo2pdf" pool-grow="4" pool-max="128"  
pool-min="4" src="org.apache.cocoon.serialization.FOPSerializer">

cocoon.xconf has this memory configuration:
   <store-janitor logger="">
      <!-- How much free memory shall be available in the jvm -->
      <parameter name="freememory" value="5000000"/>
      <!-- Indicates the limit of the jvm memory consumption. The  
default max
           heapsize for Sun's JVM is (almost) 64Mb -->
      <parameter name="heapsize" value="146000000"/>
      <!-- How often shall the cleanup thread check memory -->
      <parameter name="cleanupthreadinterval" value="10"/>
      <!-- Experimental adaptive algorithm for cleanup interval
      <parameter name="adaptivethreadinterval" value="true"/>
      <!-- Indicates the thread priority of the cleanup thread -->
      <parameter name="threadpriority" value="5"/>
      <!-- How much percent of the elements of each registered Store
           shall be removed when low on memory. Default 10% -->
      <parameter name="percent_to_free" value="10"/>
      <!-- Invoke the garbage collector when low memory is reached -->
      <parameter name="invokegc" value="false"/>

in logkit.xconf I have setup so debug level is DEBUG

- Joose

"Always remember that you are unique, just like everyone else!"
* * * +358 44 561 0270 *

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message