Mailing-List: contact users-help@continuum.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@continuum.apache.org
Received-SPF: pass (athena.apache.org: domain of oliver.lamy@gmail.com
 designates 64.233.182.186 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:sender:to:subject:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references:x-google-sender-auth;
        b=fRzi4VsXtiLSzH0QKTzdsjMejhlYgNlhim6w7Xw2MM6NQT3HHqGnmidH7NjHBMfQ6a
         QSTLJfdHYlDi0pxCAvMm5R+joy1OtQv9JO1/sy+JBm+IPxU2p9dj0p6k3Iq8MOwoej8+
         urM0BUlrkxvzApdREHIvhA9381wkvtBEoi9YA=
Message-ID: <9948cb690809051126y6ee2a2eel30eeb854f7635545@mail.gmail.com>
Date: Fri, 5 Sep 2008 20:26:11 +0200
From: "Olivier Lamy" <olamy@apache.org>
Sender: oliver.lamy@gmail.com
To: users@continuum.apache.org
Subject: Re: Continuum queuing jobs but not performing builds
In-Reply-To: <48C1550D.9020305@peterjanes.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <48BD4F74.3010604@peterjanes.ca>
	 <9e3862d80809050329t32a31c5ejc8068bf1511637e2@mail.gmail.com>
	 <48C1550D.9020305@peterjanes.ca>

Hi,

When you say "After adding a set of projects" : do you stop and
restart continuum with some projects in the queue (build or checkout
queue) ?
Are you sure about the rev you are using  691325 ? Can you have a look
at the About Page ?
When I look at the dump, I see :
at org.apache.maven.continuum.buildcontroller.DefaultBuildController.getOldScmResult(DefaultBuildController.java:776)

And line 776 [1] is a blank line.
Can you try with a 1.2 release candidate :
http://people.apache.org/builds/continuum/1.2/

As I see in the dump you are using tomcat, how do you install the war
? with a Context and docBase pointing to the builded war ?
I have had some issues with this if I didn't clean the directory
$CATALINA_HOME/webapps/continuum
BTW, I will try to reproduce this with changing manually the value in
the database.


Thanks,
--
Olivier
[1] http://fisheye6.atlassian.com/browse/continuum/trunk/continuum-core/src/main/java/org/apache/maven/continuum/buildcontroller/DefaultBuildController.java?r=691325#l776

2008/9/5 Peter Janes <continuum.apache.org@peterjanes.ca>:
> After having this happen a third time I took a closer look at the database
> and saw that one of the entries in the BUILDRESULT table had an END_TIME of
> 0.  When I changed that field to a current time and restarted the server
> Continuum started to work again.
>
> I was able to reproduce the problem by setting the END_TIME of the last
> BUILDRESULT to 0, starting the server, and waiting for that project to be
> queued.  It was resolved again when I reset END_TIME to its original value.
>
> I've reported this as http://jira.codehaus.org/browse/CONTINUUM-1871 and
> attached the thread dump.
>
> Thanks,
> Peter J.
>
> Brett Porter wrote:
>>
>> I certainly haven't seen something like this - perhaps something in the
>> project change caused an infinite loop that might be a bug in the Maven
>> project handling.
>> Are you able to get a thread dump from Continuum when it occurs?
>>
>> Thanks,
>> Brett
>>
>> 2008/9/3 Peter Janes <continuum.apache.org@peterjanes.ca>
>>
>>> Since adding a set of projects to a Continuum 1.2 instance last Thursday,
>>> the server has stopped performing any builds on any projects.  The server
>>> had performed hundreds of builds without issue over a period of several
>>> months.
>>>
>>> The initial problem that appeared was that projects would be queued but
>>> never started; as soon as the first job entered the queue Continuum would
>>> start using 100% CPU and never start building anything.  Even when I
>>> removed
>>> all of the projects from the queue it remained at 100% CPU.  Restarting
>>> the
>>> server didn't help: as soon as a job was queued the CPU would spike and
>>> no
>>> further progress would be made.
>>>
>>> Thinking that somehow the (MySQL) database might be corrupt, I removed it
>>> and started fresh.  I added the projects that appeared to cause the
>>> problem
>>> and they built successfully, so I started re-adding the rest of the
>>> projects.  Unfortunately, at some point while I was doing this builds
>>> stopped being executed again: this time they get queued up and are
>>> apparently started, but I don't see any build processes being invoked.
>>>  Even
>>> the simplest pom-only job times out.  The timeouts are shown in the
>>> Continuum log but aren't being recorded in the database as failures or
>>> errors, and restarting doesn't make a difference, which suggests to me
>>> that
>>> perhaps the database has been corrupted again.
>>>
>>> I don't see anything in Jira or the list archives; has anyone seen
>>> behaviours like this?  More importantly, has anyone been able to solve
>>> them?
>>>
>>> Environment: RHEL 5, Continuum 1.2 (built in May), Java 1.6.0_03, MySQL
>>> 5.0.45, Maven 2.0.9
>>>
>>> Peter J.
>>> --
>>> Sometimes the Universe needs a change of perspective.
>>>  --J. Michael Straczynski
>>>
>>
>>
>>
>
>
> --
> Sometimes the Universe needs a change of perspective.
>  --J. Michael Straczynski
>