[ http://jira.codehaus.org/browse/CONTINUUM-384?page=comments#action_49762 ]
witek wolejszo commented on CONTINUUM-384: ------------------------------------------ We experience the same behaviour. java version "1.5.0_03" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_03-b07) Java HotSpot(TM) Client VM (build 1.5.0_03-b07, mixed mode, sharing) Sometimes, after database errors, state of a project on the list is inconsistent (error) with state of the latest build (success). Moving to the trunk version of Derby (Version 10.1 latest snapshot * Derby 10.1.1.1 (Oct 5, 2005 / SVN 292855) does not fix the problem - replaced the library and restarted Continuum. > 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
