Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Message-ID: <27559159.1165388966784.JavaMail.jira@brutus>
Date: Tue, 5 Dec 2006 23:09:26 -0800 (PST)
From: "Vamsavardhana Reddy (JIRA)" <jira@apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Closed: (GERONIMO-803) Deploy failure during redeploy leaves
 app undeployed
In-Reply-To: <759078685.1122134806630.JavaMail.jira@ajax.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/GERONIMO-803?page=all ]

Vamsavardhana Reddy closed GERONIMO-803.
----------------------------------------

    Resolution: Fixed

Thanks Rakesh for verifying the issue.

> Deploy failure during redeploy leaves app undeployed
> ----------------------------------------------------
>
>                 Key: GERONIMO-803
>                 URL: http://issues.apache.org/jira/browse/GERONIMO-803
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: deployment
>    Affects Versions: 1.0-M3
>            Reporter: Aaron Mulder
>            Priority: Critical
>             Fix For: 1.2
>
>
> Ouch, this is a nasty one.  If you deploy app Foo, then change it to be broken (invalid DD, whatever) and redeploy it, it goes like this:
> 1) undeploy old one
> 2) try to deploy new one
> 3) fail
> The result is that the old one has been undeployed but the new one hasn't been deployed.  It would be ideal if we could "try" the deploy operation first, and only if it appears valid, undeploy the old version and start the new version.  I'm not sure how that could be done.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira