You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Robby Pelssers <ro...@ciber.com> on 2010/06/29 14:43:27 UTC
memory leak in PoolableProxyHandler
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
Kind regards,
Robby
Re: memory leak in PoolableProxyHandler
Posted by Jasha Joachimsthal <j....@onehippo.com>.
On 30 June 2010 10:14, Robby Pelssers <ro...@ciber.com> wrote:
> One question:
>
>
>
> Yesterday I downloaded the sources from
> cocoon/tags/cocoon-2.2/cocoon-sitemap-impl/cocoon-sitemap/impl-1.0.0. Next
> I made the necessary code change and installed the artifact in my local
> maven repo.
>
>
>
> But this does not ensure unfortunately that my colleague(s) use the same
> patched artifact. What would be the best way forward for me in this case
> since you only applied the patch to trunk which is a snapshot version.
>
>
>
> Cheers,
>
> Robby
>
The quickest way is to deploy it to your local Maven repository with the SVN
revision number in the name of the jar. The best way is to get it released
but that may take some time.
Jasha Joachimsthal
j.joachimsthal@onehippo.com - jasha@apache.org
www.onehippo.com
Amsterdam - Hippo B.V. Oosteinde 11 1017 WT Amsterdam +31(0)20-5224466
San Francisco - Hippo USA Inc. 185 H Street, suite B, Petaluma CA 94952 +1
(707) 7734646
RE: memory leak in PoolableProxyHandler
Posted by Robby Pelssers <ro...@ciber.com>.
One question:
Yesterday I downloaded the sources from cocoon/tags/cocoon-2.2/cocoon-sitemap-impl/cocoon-sitemap/impl-1.0.0. Next I made the necessary code change and installed the artifact in my local maven repo.
But this does not ensure unfortunately that my colleague(s) use the same patched artifact. What would be the best way forward for me in this case since you only applied the patch to trunk which is a snapshot version.
Cheers,
Robby
Re: memory leak in PoolableProxyHandler
Posted by Jasha Joachimsthal <j....@onehippo.com>.
And done applying the patch, thanks Alexander for submitting it.
Jasha
On 30 June 2010 09:21, Jasha Joachimsthal <j....@onehippo.com>wrote:
> Working on it... ;-)
>
> Jasha Joachimsthal
>
> j.joachimsthal@onehippo.com - jasha@apache.org
>
> www.onehippo.com
> Amsterdam - Hippo B.V. Oosteinde 11 1017 WT Amsterdam +31(0)20-5224466
> San Francisco - Hippo USA Inc. 185 H Street, suite B, Petaluma CA 94952 +1
> (707) 7734646
>
>
>
>
>
>
>
> On 30 June 2010 09:05, Robby Pelssers <ro...@ciber.com> wrote:
>
>> 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.daniel@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-unsubscribe@cocoon.apache.org
>> For additional commands, e-mail: users-help@cocoon.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
>> For additional commands, e-mail: users-help@cocoon.apache.org
>>
>>
>
Re: memory leak in PoolableProxyHandler
Posted by Jasha Joachimsthal <j....@onehippo.com>.
Working on it... ;-)
Jasha Joachimsthal
j.joachimsthal@onehippo.com - jasha@apache.org
www.onehippo.com
Amsterdam - Hippo B.V. Oosteinde 11 1017 WT Amsterdam +31(0)20-5224466
San Francisco - Hippo USA Inc. 185 H Street, suite B, Petaluma CA 94952 +1
(707) 7734646
On 30 June 2010 09:05, Robby Pelssers <ro...@ciber.com> wrote:
> 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.daniel@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-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>
>
RE: memory leak in PoolableProxyHandler
Posted by Robby Pelssers <ro...@ciber.com>.
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.daniel@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-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: memory leak in PoolableProxyHandler
Posted by Alexander Daniel <al...@gmx.at>.
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-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org