I'm dissapointed to have come to the same conclusion. It's really a huge memory leak.
My settings for tomcat were JAVA_OPTS="-Xnoclassgc -Xss1536k -Xms1536m -Xmx1536m -XX:NewSize=128m -XX:MaxNewSize=128m -XX:SurvivorRatio=2 -XX:+DisableExplicitGC -Xloggc:/home/pxprod1/logs/GC_tomcat_productinformation.log -Dorg.apache.cocoon.mode=prod" I created a few cocoon services over the last few weeks which had to transform about 10.000 products. After about 5000 products I ran into java.lang.OutOfMemoryError: Java heap space. This was quite consistent behaviour and after a day of profiling using Jrockit Management Console and Yourkit Java Profiler my investigations led to this issue. Why is this patch not being committed to trunk if it is such severe? Ps. I think I'm confident to say I can lower the memory settings now to < 800mb after applying the patch. Kind regards, Robby Pelssers -----Original Message----- From: Alexander Daniel [mailto:alexander.dan...@gmx.at] Sent: Tuesday, June 29, 2010 8:19 PM To: users@cocoon.apache.org Subject: Re: memory leak in PoolableProxyHandler On 29.06.2010, at 14:43, Robby Pelssers wrote: > Can anyone tell me if the latest stable build downloadable from Cocoon2.2 > home page contains the fix for the issue below? > > https://issues.apache.org/jira/browse/COCOON-2259 Unfortunately not. The patch is even not committed to the trunk. Alex --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@cocoon.apache.org For additional commands, e-mail: users-h...@cocoon.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@cocoon.apache.org For additional commands, e-mail: users-h...@cocoon.apache.org
