camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Schneider <ch...@die-schneider.net>
Subject Re: Build failed in Jenkins: Camel.trunk.fulltest #329
Date Mon, 13 Jun 2011 06:53:23 GMT
Hi Claus and Willem,

I lowered the maxpermsize and max heap size before as my changes caused 
the build to use much less memory. As it seems we were probably at the 
limit of the lower settings.
So as Claus did not change that much our memory consumption is probably 
just over the lower heap or perm size. Should we try to figure out a 
lower working setting then 1024 and 512?
I am not sure but I can imagine that our high settings take quite a lot 
of the resources of the build servers.

Christian


Am 13.06.2011 08:36, schrieb Willem Jiang:
> Hi Claus,
>
> I think the max memory size is a little lower, we could raise the 
> option of -Xmx, but I think the setting PermSize size is enough.
>
>
> On 6/13/11 1:54 PM, Claus Ibsen wrote:
>> Hi
>>
>> Jenkins runs out of memory. But thats no wonder when the MAVEN_OPTS is
>> changed to be soo low
>>
>> -da -dsa -XX:MaxPermSize=256m -Xmx512m
>>
>> It used to be set to 1024m. So I will set it back. Also raise the
>> PermSize as well.
>>
>
>

-- 
Christian Schneider
http://www.liquid-reality.de

Open Source Architect
http://www.talend.com


Mime
View raw message