You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ace.apache.org by "Toni Menzel (JIRA)" <ji...@apache.org> on 2009/10/06 15:57:31 UTC
[jira] Created: (ACE-51) Take over zombie gateways
Take over zombie gateways
-------------------------
Key: ACE-51
URL: https://issues.apache.org/jira/browse/ACE-51
Project: Ace
Issue Type: Improvement
Reporter: Toni Menzel
Not sure if it is against the system but i just got the problem that i switched servers/repository instances (turn off the old, turn on another).
Now, some gateways still have an old state which cannot be changed (at least not in a controled way) with the new server instance
I would imagine a way to "take over" such gateways by reverting to version 0 or make a new version with no bundle in it (maybe better) so that the new server can continue with controling this instance.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ACE-51) Take over zombie gateways
Posted by "Marcel Offermans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12762720#action_12762720 ]
Marcel Offermans commented on ACE-51:
-------------------------------------
Adding a feature to the management agent to uninstall the currently installed deployment package should be enough to achieve that. Subsequently, the management agent can contact the new server again and get the latest version of the software configured for it.
In cases where the current version somehow has stopped working completely, this might also be something you want to do, even if you're not switching servers or anything.
> Take over zombie gateways
> -------------------------
>
> Key: ACE-51
> URL: https://issues.apache.org/jira/browse/ACE-51
> Project: Ace
> Issue Type: Improvement
> Reporter: Toni Menzel
>
> Not sure if it is against the system but i just got the problem that i switched servers/repository instances (turn off the old, turn on another).
> Now, some gateways still have an old state which cannot be changed (at least not in a controled way) with the new server instance
> I would imagine a way to "take over" such gateways by reverting to version 0 or make a new version with no bundle in it (maybe better) so that the new server can continue with controling this instance.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ACE-51) Take over zombie gateways
Posted by "Toni Menzel (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12762918#action_12762918 ]
Toni Menzel commented on ACE-51:
--------------------------------
Thats sounds like a plan.
But i see its an activity initiated by the management agent, correct ?
In the end, sure, the management agents is seeing that that is something wrong with the server (if it responds, versions are lower), so it could make this reinit fully out of its own judgement.
But it could also be that the server sends a some "reset yourself" as part of the polling reply.
Then things work similar to this iphone "remote reset" calls.
Anyhow, i think this gets crucual while experimenting and working more management agents that are treatened as arbitrary containers that are at best never again touched physically.
> Take over zombie gateways
> -------------------------
>
> Key: ACE-51
> URL: https://issues.apache.org/jira/browse/ACE-51
> Project: Ace
> Issue Type: Improvement
> Reporter: Toni Menzel
>
> Not sure if it is against the system but i just got the problem that i switched servers/repository instances (turn off the old, turn on another).
> Now, some gateways still have an old state which cannot be changed (at least not in a controled way) with the new server instance
> I would imagine a way to "take over" such gateways by reverting to version 0 or make a new version with no bundle in it (maybe better) so that the new server can continue with controling this instance.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.