cocoon 2.0.4 and cocoon 2.1.6 on tomcat 5.0, redhat 9, with apache at front, serving several cocoon based web sites
the box: piv 2.4 1G Ram periodicaly tomcat hangs and needs restart i dont have figure until know what cause the problem On Wed, 16 Feb 2005, Michael Wechner wrote: > Has anyone experienced a Cocoon application which stopped at some point > responding to requests and hangs? > > For instance if the hardware can handle only a certain amout of requests > (which is always the case) and handling becomes slower and slower and > more threads are being opened and at some point it just stops, but > cannot recover and hangs ... > > Also what is difference between > <thread-pools> > <!--+ > | This is the default thread pool. It's use fits best for short > | running background tasks. > +--> > <thread-pool> > <name>default</name> > <priority>NORM</priority> > <daemon>false</daemon> > <queue-size>-1</queue-size> > <max-pool-size>5</max-pool-size> > <min-pool-size>5</min-pool-size> > <keep-alive-time-ms>60000</keep-alive-time-ms> > <block-policy>RUN</block-policy> > <shutdown-graceful>false</shutdown-graceful> > <shutdown-wait-time-ms>-1</shutdown-wait-time-ms> > </thread-pool> > <!--+ > | This thread pool should be used for daemons (permanently running > | threads). > +--> > <thread-pool> > <name>daemon</name> > <priority>NORM</priority> > <daemon>true</daemon> > <queue-size>0</queue-size> > <max-pool-size>-1</max-pool-size> > <min-pool-size>1</min-pool-size> > <keep-alive-time-ms>60000</keep-alive-time-ms> > <block-policy>ABORT</block-policy> > <shutdown-graceful>false</shutdown-graceful> > <shutdown-wait-time-ms>-1</shutdown-wait-time-ms> > </thread-pool> > </thread-pools> > > > I couldn't find any good documentation on this configuration within > cocoon.xconf. > > Thanks > > Michi > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
