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/28 17:29:26 UTC
[jira] Created: (CONTINUUM-2371) Unable to view queues after loss
of build agent
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
[jira] Updated: (CONTINUUM-2371) Unable to view queues after loss
of build agent
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-2371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated CONTINUUM-2371:
------------------------------------
Fix Version/s: (was: 1.3.5)
1.4.0
> 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
> Fix For: 1.4.0
>
>
> 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
[jira] Commented: (CONTINUUM-2371) Unable to view queues after loss
of build agent
Posted by "Wendy Smoak (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-2371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=192807#action_192807 ]
Wendy Smoak commented on CONTINUUM-2371:
----------------------------------------
Related thread: http://www.nabble.com/What-should-happen-when-a-distributed-agent-dies--td25649131.html
> 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
[jira] Assigned: (CONTINUUM-2371) Unable to view queues after loss
of build agent
Posted by "Maria Catherine Tan (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-2371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maria Catherine Tan reassigned CONTINUUM-2371:
----------------------------------------------
Assignee: Maria Catherine Tan
> 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 (Beta)
> Reporter: Wendy Smoak
> Assignee: Maria Catherine Tan
> Fix For: 1.4.1 (Beta)
>
>
> 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
[jira] Updated: (CONTINUUM-2371) Unable to view queues after loss
of build agent
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-2371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated CONTINUUM-2371:
------------------------------------
Fix Version/s: (was: 1.4.1 (Beta))
1.4.0 (Beta)
> 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 (Beta)
> Reporter: Wendy Smoak
> Assignee: Maria Catherine Tan
> Fix For: 1.4.0 (Beta)
>
>
> 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
[jira] Closed: (CONTINUUM-2371) Unable to view queues after loss of
build agent
Posted by "Maria Catherine Tan (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-2371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maria Catherine Tan closed CONTINUUM-2371.
------------------------------------------
Resolution: Fixed
fixed in r926483
1. check if the agent is available by calling the ping method before proceeding with the call to other methods
2. if the agent is not available, disable it.
> 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 (Beta)
> Reporter: Wendy Smoak
> Assignee: Maria Catherine Tan
> Fix For: 1.4.1 (Beta)
>
>
> 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
[jira] Updated: (CONTINUUM-2371) Unable to view queues after loss
of build agent
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-2371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated CONTINUUM-2371:
------------------------------------
Fix Version/s: 1.3.5
> 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
> Fix For: 1.3.5
>
>
> 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
[jira] Commented: (CONTINUUM-2371) Unable to view queues after loss
of build agent
Posted by "Wendy Smoak (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (CONTINUUM-2371) Unable to view queues after loss
of build agent
Posted by "Maria Catherine Tan (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-2371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=215050#action_215050 ]
Maria Catherine Tan commented on CONTINUUM-2371:
------------------------------------------------
Added unit test in r926826
Update documentation in r926839
> 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 (Beta)
> Reporter: Wendy Smoak
> Assignee: Maria Catherine Tan
> Fix For: 1.4.1 (Beta)
>
>
> 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
[jira] Commented: (CONTINUUM-2371) Unable to view queues after loss
of build agent
Posted by "Wendy Smoak (JIRA)" <ji...@codehaus.org>.
[ 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