Mailing-List: contact issues-help@continuum.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@continuum.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Message-ID: 
 <19891890.91254258515258.JavaMail.haus-jira@codehaus01.managed.contegix.com>
Date: Tue, 29 Sep 2009 16:08:35 -0500 (CDT)
From: "Wendy Smoak (JIRA)" <jira@codehaus.org>
To: issues@continuum.apache.org
Subject: [jira] Commented: (CONTINUUM-2371) Unable to view queues after loss
 of build agent
In-Reply-To: 
 <17400756.15251254151766936.JavaMail.haus-jira@codehaus01.managed.contegix.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


    [ http://jira.codehaus.org/browse/CONTINUUM-2371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=192803#action_192803 ] 

Wendy Smoak commented on CONTINUUM-2371:
----------------------------------------

Even after deleting the dead build agent, the Queues page still shows an error.

Apparently the system is still trying to get information from the agent, even after it has been deleted.

Possibly related, I notice that the continuum.xml config file still contains this deleted agent.

A re-start syncs up the continuum.xml file with reality and makes the Queues page work again.

It should not be necessary to re-start in this situation.

> Unable to view queues after loss of build agent
> -----------------------------------------------
>
>                 Key: CONTINUUM-2371
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-2371
>             Project: Continuum
>          Issue Type: Bug
>          Components: Distributed Builds
>    Affects Versions: 1.3.4
>            Reporter: Wendy Smoak
>
> When a build agent goes down unexpectedly, the system does not handle it gracefully.
> The Queues page (/displayQueues!display.action) shows Error Occurred org.apache.maven.continuum.ContinuumException: Error retrieving projects currently preparing build in http://localhost:8181/continuum-buildagent/xmlrpc 
> To reproduce, add 2 or more agents, force a bunch of builds, then stop one of the agents without disabling it from the master.
> I notice  that the Build Agents page (/buildAgentList.action) still shows the agent as Enabled=true, even though it is not responding.
> There should probably be some concept of the system automatically disabling an agent that is not behaving correctly.  For now I'd be happy with the admin having to manually re-enable it, but an auto-recovery feature might be a nice enhancement for later.

-- 
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