You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@continuum.apache.org by "Wendy Smoak (JIRA)" <ji...@codehaus.org> on 2009/09/29 22:58:35 UTC

[jira] Commented: (CONTINUUM-2371) Unable to view queues after loss of build agent

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

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

The second time I tried this, I was able to edit and disable the build agent which had been lost, however the Queues page still showed the error.

Removing the bad agent from the build agent group also did not help.

If an agent is disabled, I don't think it should be contacted to see what is in its queue.  

If it is going to be contacted, then the system needs to handle the case where it is not reachable.

> 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