You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Valentin Mahrwald (JIRA)" <ji...@apache.org> on 2011/01/17 09:07:44 UTC
[jira] Closed: (ARIES-528) Rollback behaviour for application
update does not work
[ https://issues.apache.org/jira/browse/ARIES-528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Valentin Mahrwald closed ARIES-528.
-----------------------------------
Resolution: Fixed
Cleaning out issue that was resolved with #1054062.
> Rollback behaviour for application update does not work
> -------------------------------------------------------
>
> Key: ARIES-528
> URL: https://issues.apache.org/jira/browse/ARIES-528
> Project: Aries
> Issue Type: Bug
> Components: Application
> Affects Versions: 0.3
> Reporter: Valentin Mahrwald
> Assignee: Valentin Mahrwald
>
> The desired behaviour of AriesApplicationManager.update is to attempt a new deployment but rollback to the consistent state in case of problems.
> Currently this does not work for two reasons:
> a) When rolling back to the previous version the wrong deployment metadata gets used, so that the rollback erroneously tries to install the new version again rather than the old one.
> b) In isolated cases some failures during installation can leave behind a broken framework that prevents any further installs from succeeding.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.