continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Olivier Lamy (JIRA)" <>
Subject [jira] Commented: (CONTINUUM-1871) Continuum does not execute builds when last BUILDRESULT.END_TIME=0
Date Sun, 07 Sep 2008 14:36:48 GMT


Olivier Lamy commented on CONTINUUM-1871:

The best to fix this should be to use a new method in buildResultDao buildResultDao.getBuildResultsForProject(
projectId, buildResultId ).
This method must return all BuildResult with an id >= buildResultId.
This will prevent memory use if the lastBuildResult has an endTime of 0.

> Continuum does not execute builds when last BUILDRESULT.END_TIME=0
> ------------------------------------------------------------------
>                 Key: CONTINUUM-1871
>                 URL:
>             Project: Continuum
>          Issue Type: Bug
>    Affects Versions: 1.2
>         Environment: RHEL 5, Continuum 1.2 (SVN 691325), Java 1.6.0_03, MySQL 5.0.45,
Maven 2.0.9
>            Reporter: Peter Janes
>             Fix For: 1.2.1
>         Attachments: thread-dump.txt, thread-dump.txt
> After adding a set of projects to a Continuum 1.2 instance, the server stopped performing
any builds on any projects.  CPU usage shoots up to 100%, projects are queued up and are apparently
started, but no build processes are invoked.  Even the simplest pom-only job times out.
> Looking at the database I noticed that the last entry for the top-queued project 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 perform builds again.
> I was able to duplicate the problem by setting the END_TIME of the last BUILDRESULT of
a project to 0, starting the server, and waiting for that project to be queued.  The problem
was resolved again when I reset END_TIME to its original value.
> I've attached a thread dump as suggested on users@continuum.  It seems to show that Continuum
is in the SCM module's ChangeSet.toString(), which doesn't seem right, but perhaps it will
help point to the root cause.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message