You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org> on 2005/07/23 18:06:46 UTC
[jira] Created: (GERONIMO-803) Deploy failure during redeploy leaves app undeployed
Deploy failure during redeploy leaves app undeployed
----------------------------------------------------
Key: GERONIMO-803
URL: http://issues.apache.org/jira/browse/GERONIMO-803
Project: Geronimo
Type: Bug
Components: deployment
Versions: 1.0-M3
Reporter: Aaron Mulder
Fix For: 1.0
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
[jira] Commented: (GERONIMO-803) Deploy failure during redeploy
leaves app undeployed
Posted by "Rakesh Midha (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-803?page=comments#action_12453500 ]
Rakesh Midha commented on GERONIMO-803:
---------------------------------------
This works fine now. I tried tis scenerio and it gave me right results. If newconfig fails the old one is started.
> 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
[jira] Updated: (GERONIMO-803) Deploy failure during redeploy
leaves app undeployed
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-803?page=all ]
Aaron Mulder updated GERONIMO-803:
----------------------------------
Fix Version: 1.1
(was: 1.2)
Priority: Critical (was: Major)
Should be fixed, just need to test.
> Deploy failure during redeploy leaves app undeployed
> ----------------------------------------------------
>
> Key: GERONIMO-803
> URL: http://issues.apache.org/jira/browse/GERONIMO-803
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: deployment
> Versions: 1.0-M3
> Reporter: Aaron Mulder
> Assignee: Aaron Mulder
> Priority: Critical
> Fix For: 1.1
>
> 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
[jira] Assigned: (GERONIMO-803) Deploy failure during redeploy
leaves app undeployed
Posted by "Dain Sundstrom (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-803?page=all ]
Dain Sundstrom reassigned GERONIMO-803:
---------------------------------------
Assign To: Dain Sundstrom
> Deploy failure during redeploy leaves app undeployed
> ----------------------------------------------------
>
> Key: GERONIMO-803
> URL: http://issues.apache.org/jira/browse/GERONIMO-803
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: deployment
> Versions: 1.0-M3
> Reporter: Aaron Mulder
> Assignee: Dain Sundstrom
> 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
[jira] Updated: (GERONIMO-803) Deploy failure during redeploy
leaves app undeployed
Posted by "Matt Hogstrom (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-803?page=all ]
Matt Hogstrom updated GERONIMO-803:
-----------------------------------
Fix Version: 1.2
(was: 1.1)
> Deploy failure during redeploy leaves app undeployed
> ----------------------------------------------------
>
> Key: GERONIMO-803
> URL: http://issues.apache.org/jira/browse/GERONIMO-803
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: deployment
> Versions: 1.0-M3
> Reporter: Aaron Mulder
> Assignee: 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
[jira] Closed: (GERONIMO-803) Deploy failure during redeploy leaves
app undeployed
Posted by "Vamsavardhana Reddy (JIRA)" <ji...@apache.org>.
[ 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
[jira] Updated: (GERONIMO-803) Deploy failure during redeploy
leaves app undeployed
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-803?page=all ]
Aaron Mulder updated GERONIMO-803:
----------------------------------
Assign To: (was: Aaron Mulder)
> Deploy failure during redeploy leaves app undeployed
> ----------------------------------------------------
>
> Key: GERONIMO-803
> URL: http://issues.apache.org/jira/browse/GERONIMO-803
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: deployment
> 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
[jira] Commented: (GERONIMO-803) Deploy failure during redeploy
leaves app undeployed
Posted by "Matt Hogstrom (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-803?page=comments#action_12450419 ]
Matt Hogstrom commented on GERONIMO-803:
----------------------------------------
Aaron, can you confirm this is fixed?
> 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
[jira] Assigned: (GERONIMO-803) Deploy failure during redeploy
leaves app undeployed
Posted by "Dain Sundstrom (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-803?page=all ]
Dain Sundstrom reassigned GERONIMO-803:
---------------------------------------
Assign To: Aaron Mulder (was: Dain Sundstrom)
I added a reloadConfiguration(id, newVersion) command to ConfigurationManager. This command will attempt to load and/or start a new version of the configuration. If the new configuration fails to load or start, the old ConfigurationManager will attempt to restart the old configuration.
> Deploy failure during redeploy leaves app undeployed
> ----------------------------------------------------
>
> Key: GERONIMO-803
> URL: http://issues.apache.org/jira/browse/GERONIMO-803
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: deployment
> Versions: 1.0-M3
> Reporter: Aaron Mulder
> Assignee: Aaron Mulder
> 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
[jira] Updated: (GERONIMO-803) Deploy failure during redeploy leaves app undeployed
Posted by "Matt Hogstrom (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-803?page=all ]
Matt Hogstrom updated GERONIMO-803:
-----------------------------------
Fix Version: 1.1
(was: 1.0)
Moving to 1.1
> Deploy failure during redeploy leaves app undeployed
> ----------------------------------------------------
>
> Key: GERONIMO-803
> URL: http://issues.apache.org/jira/browse/GERONIMO-803
> Project: Geronimo
> Type: Bug
> Components: deployment
> Versions: 1.0-M3
> Reporter: Aaron Mulder
> Fix For: 1.1
>
> 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