From issues-return-1584-apmail-continuum-issues-archive=continuum.apache.org@continuum.apache.org Sun Sep 07 14:21:48 2008 Return-Path: Delivered-To: apmail-continuum-issues-archive@www.apache.org Received: (qmail 86623 invoked from network); 7 Sep 2008 14:21:48 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 7 Sep 2008 14:21:48 -0000 Received: (qmail 95434 invoked by uid 500); 7 Sep 2008 14:21:46 -0000 Delivered-To: apmail-continuum-issues-archive@continuum.apache.org Received: (qmail 95419 invoked by uid 500); 7 Sep 2008 14:21:46 -0000 Mailing-List: contact issues-help@continuum.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@continuum.apache.org Delivered-To: mailing list issues@continuum.apache.org Received: (qmail 95408 invoked by uid 99); 7 Sep 2008 14:21:46 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 07 Sep 2008 07:21:46 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [63.246.2.115] (HELO codehaus01.managed.contegix.com) (63.246.2.115) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 07 Sep 2008 14:20:48 +0000 Received: from codehaus01.managed.contegix.com (localhost.localdomain [127.0.0.1]) by codehaus01.managed.contegix.com (Postfix) with ESMTP id 0947614A8015 for ; Sun, 7 Sep 2008 09:20:48 -0500 (CDT) Message-ID: <26487381.1220797248837.JavaMail.haus-jira@codehaus01.managed.contegix.com> Date: Sun, 7 Sep 2008 09:20:48 -0500 (CDT) From: "Olivier Lamy (JIRA)" To: issues@continuum.apache.org Subject: [jira] Commented: (CONTINUUM-1871) Continuum does not execute builds when last BUILDRESULT.END_TIME=0 In-Reply-To: <29134760.1220629609474.JavaMail.haus-jira@codehaus01.managed.contegix.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ http://jira.codehaus.org/browse/CONTINUUM-1871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147263#action_147263 ] Olivier Lamy commented on CONTINUUM-1871: ----------------------------------------- The explanation seems to be the following : Continuum has certainly been stopped abrutly (killed) when project was building. In this case the oldBuildResult of this project is 0. During the next build, continuum try to load all scmChange since the last buildResult. If the oldBuildResult has an endTime of 0 : all scmResult since the project has been added in Continuum will be loaed. This cause a very huge memory (due to a lof of String concat in ChangeSet.toString() method) when the project has a big history in the database. > Continuum does not execute builds when last BUILDRESULT.END_TIME=0 > ------------------------------------------------------------------ > > Key: CONTINUUM-1871 > URL: http://jira.codehaus.org/browse/CONTINUUM-1871 > 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: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira