You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by Antoine Toulme <an...@lunar-ocean.com> on 2010/07/08 23:39:41 UTC
Fwd: [Hudson] ODE-trunk-m2-jdk5-nightly-deploy » #7 stuck, so killed it
FYI. This is the second time this happens. I also had to kill a build
yesterday that used maven.
---------- Forwarded message ----------
From: sebb <se...@gmail.com>
Date: Thu, Jul 8, 2010 at 14:36
Subject: [Hudson] ODE-trunk-m2-jdk5-nightly-deploy » #7 stuck, so killed it
To: builds@apache.org
ODE-trunk-m2-jdk5-nightly-deploy » #7 was stuck - it had run out of
PermGen space.
Hudson should have tidied up, but did not, so I killed the job a few
times from the GUI and it seemed to recover.
Not sure why Hudson can do this itself ...
Re: Fwd: [Hudson] ODE-trunk-m2-jdk5-nightly-deploy » #7 stuck, so killed it
Posted by David Carver <d_...@yahoo.com>.
Depending on the version of Hudson in use, you should find this under
the Advanced button for the goal configuration (where you can specify an
alternative pom file to use). If that doesn't work, you should be able
to add Paramters to the build and make one of those paramaters
JAVA_OPTS...this sets it as an environment variable, and maven should
pick those up.
Dave
On 07/08/2010 02:57 PM, Tammo van Lessen wrote:
> Yes, I didn't find the time yet to see how to set the MAVEN_OPTS in the
> hudson build. I'll try to figure it out now.
>
> On 08.07.2010 23:53, David Carver wrote:
>> My experience with ODE and Hudson builds regardless if it's Maven or
>> Buildr you need to specify at least the JVM option of
>> -XX:MaxPermSize=256m if you are using a Sun JVM for the build.
>>
>> It also helps to specify, -Xmx2048m -Xms512m
>>
>> I've in the past set up a Parameter based build, with JAVA_OPTS and the
>> values of:
>>
>> -XX:MaxPermSize=256m -Xmx2048m -Xms512m
>>
>> The permgen errors typically happen during Hibernate code generation steps.
>>
>> Dave
>>
>>
>> On 07/08/2010 02:39 PM, Antoine Toulme wrote:
>>> FYI. This is the second time this happens. I also had to kill a build
>>> yesterday that used maven.
>>>
>>> ---------- Forwarded message ----------
>>> From: sebb<se...@gmail.com>
>>> Date: Thu, Jul 8, 2010 at 14:36
>>> Subject: [Hudson] ODE-trunk-m2-jdk5-nightly-deploy » #7 stuck, so
>>> killed it
>>> To: builds@apache.org
>>>
>>>
>>> ODE-trunk-m2-jdk5-nightly-deploy » #7 was stuck - it had run out of
>>> PermGen space.
>>>
>>> Hudson should have tidied up, but did not, so I killed the job a few
>>> times from the GUI and it seemed to recover.
>>>
>>> Not sure why Hudson can do this itself ...
>>>
Re: Fwd: [Hudson] ODE-trunk-m2-jdk5-nightly-deploy » #7 stuck, so killed it
Posted by Tammo van Lessen <tv...@gmail.com>.
Yes, I didn't find the time yet to see how to set the MAVEN_OPTS in the
hudson build. I'll try to figure it out now.
On 08.07.2010 23:53, David Carver wrote:
> My experience with ODE and Hudson builds regardless if it's Maven or
> Buildr you need to specify at least the JVM option of
> -XX:MaxPermSize=256m if you are using a Sun JVM for the build.
>
> It also helps to specify, -Xmx2048m -Xms512m
>
> I've in the past set up a Parameter based build, with JAVA_OPTS and the
> values of:
>
> -XX:MaxPermSize=256m -Xmx2048m -Xms512m
>
> The permgen errors typically happen during Hibernate code generation steps.
>
> Dave
>
>
> On 07/08/2010 02:39 PM, Antoine Toulme wrote:
>> FYI. This is the second time this happens. I also had to kill a build
>> yesterday that used maven.
>>
>> ---------- Forwarded message ----------
>> From: sebb<se...@gmail.com>
>> Date: Thu, Jul 8, 2010 at 14:36
>> Subject: [Hudson] ODE-trunk-m2-jdk5-nightly-deploy » #7 stuck, so
>> killed it
>> To: builds@apache.org
>>
>>
>> ODE-trunk-m2-jdk5-nightly-deploy » #7 was stuck - it had run out of
>> PermGen space.
>>
>> Hudson should have tidied up, but did not, so I killed the job a few
>> times from the GUI and it seemed to recover.
>>
>> Not sure why Hudson can do this itself ...
>>
>
--
Tammo van Lessen - http://www.taval.de
Re: Fwd: [Hudson] ODE-trunk-m2-jdk5-nightly-deploy » #7 stuck, so killed it
Posted by David Carver <d_...@yahoo.com>.
My experience with ODE and Hudson builds regardless if it's Maven or
Buildr you need to specify at least the JVM option of
-XX:MaxPermSize=256m if you are using a Sun JVM for the build.
It also helps to specify, -Xmx2048m -Xms512m
I've in the past set up a Parameter based build, with JAVA_OPTS and the
values of:
-XX:MaxPermSize=256m -Xmx2048m -Xms512m
The permgen errors typically happen during Hibernate code generation steps.
Dave
On 07/08/2010 02:39 PM, Antoine Toulme wrote:
> FYI. This is the second time this happens. I also had to kill a build
> yesterday that used maven.
>
> ---------- Forwarded message ----------
> From: sebb<se...@gmail.com>
> Date: Thu, Jul 8, 2010 at 14:36
> Subject: [Hudson] ODE-trunk-m2-jdk5-nightly-deploy » #7 stuck, so killed it
> To: builds@apache.org
>
>
> ODE-trunk-m2-jdk5-nightly-deploy » #7 was stuck - it had run out of
> PermGen space.
>
> Hudson should have tidied up, but did not, so I killed the job a few
> times from the GUI and it seemed to recover.
>
> Not sure why Hudson can do this itself ...
>