Return-Path: Delivered-To: apmail-maven-continuum-dev-archive@www.apache.org Received: (qmail 40321 invoked from network); 10 Nov 2005 05:24:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 10 Nov 2005 05:24:29 -0000 Received: (qmail 23957 invoked by uid 500); 10 Nov 2005 05:24:29 -0000 Delivered-To: apmail-maven-continuum-dev-archive@maven.apache.org Received: (qmail 23893 invoked by uid 500); 10 Nov 2005 05:24:28 -0000 Mailing-List: contact continuum-dev-help@maven.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: continuum-dev@maven.apache.org Delivered-To: mailing list continuum-dev@maven.apache.org Received: (qmail 23882 invoked by uid 99); 10 Nov 2005 05:24:28 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Nov 2005 21:24:28 -0800 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=DNS_FROM_RFC_ABUSE X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [63.246.20.114] (HELO 63-246-20-114.contegix.com) (63.246.20.114) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Nov 2005 21:24:21 -0800 Received: (qmail 5620 invoked by uid 89); 10 Nov 2005 05:24:06 -0000 Received: from unknown (HELO codehaus01.managed.contegix.com) (127.0.0.1) by smtp.domain.com with SMTP; 10 Nov 2005 05:24:06 -0000 Message-ID: <95191563.1131600246243.JavaMail.haus-jira@codehaus01.managed.contegix.com> Date: Wed, 9 Nov 2005 23:24:06 -0600 (CST) From: "Andrew Moore (JIRA)" To: continuum-dev@maven.apache.org Subject: [jira] Commented: (CONTINUUM-384) Build Error while queueing projects to be built In-Reply-To: <8076266.1130498711791.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 X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://jira.codehaus.org/browse/CONTINUUM-384?page=comments#action_50532 ] Andrew Moore commented on CONTINUUM-384: ---------------------------------------- I am also seeing this. Manually kicking off a build directly after build failure notification usually works. java version "1.4.2_09" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_09-b05) Java HotSpot(TM) Client VM (build 1.4.2_09-b05, mixed mode) Linux 2.4.10-64GB-SMP #1 SMP Fri Sep 28 17:26:36 GMT 2001 unknown > Build Error while queueing projects to be built > ----------------------------------------------- > > Key: CONTINUUM-384 > URL: http://jira.codehaus.org/browse/CONTINUUM-384 > Project: Continuum > Type: Bug > Components: continuum-core > Versions: 1.0 > Environment: Linux running JDK 1.5.0_01 > Reporter: Bob Allison > Attachments: wrapper.log > > > I get periodic deadlock exceptions from Derby while building projects. It does not happen regularly, just occasionally. I have two projects (IDs 1 and 7) which are on a schedule to run every 15 minutes, and I have had the problem occur four times in the last 18 hours. I have a third project (ID 6) which runs once each day; there was no problem at the time it was scheduled to run. Attached is a file with snippets from wrapper.log which show the entire log from the four runs of the schedule which had a failure. -- 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