You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Prasad Kashyap (JIRA)" <de...@geronimo.apache.org> on 2006/05/03 18:30:46 UTC
[jira] Created: (GERONIMO-1974) Listing WARs portlet broken after a
redeploy using CLI
Listing WARs portlet broken after a redeploy using CLI
------------------------------------------------------
Key: GERONIMO-1974
URL: http://issues.apache.org/jira/browse/GERONIMO-1974
Project: Geronimo
Type: Bug
Security: public (Regular issues)
Components: console
Versions: 1.1
Reporter: Prasad Kashyap
Assigned to: Aaron Mulder
Priority: Blocker
Fix For: 1.1
After a redeploy is done by CLI, the portlet in the console that displays the list is broken.
(http://localhost:8080/console/portal/apps/apps_war). It shows the message, "Error occurred in portlet!" . It needs a server restart to fix this problem. Stacktrace attached.
--
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] Reopened: (GERONIMO-1974) Listing WARs portlet broken after
a redeploy using CLI
Posted by "Prasad Kashyap (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1974?page=all ]
Prasad Kashyap reopened GERONIMO-1974:
--------------------------------------
I did a redeploy test on the latest code and this is what I found now.
Here's the command:
deploy --user system --password manager redeploy C:\Apache\geronimo2\applications\welcome\target\geronimo-welcome-1.2-SNAPSHOT.war C:\Apache\geronimo2\configs\welcome-jetty\target\plan\plan.xml geronimo/welcome-jetty/1.1-SNAPSHOT/car
Here's the error message:
Redeployed geronimo/welcome-jetty/1.2-SNAPSHOT/car
Error: Operation failed: Trying to stop unknown configuration:
geronimo/welcome-jetty/1.2-SNAPSHOT/car
Refreshing the list in the console, I still get the message in the portlet,
"Error occurred in portlet!"
Same stacktrace as posted earlier in this thread.
Reopening http://issues.apache.org/jira/browse/GERONIMO-1974
Also see, http://www.mail-archive.com/dev@geronimo.apache.org/msg21827.html
Cheers
Prasad
> Listing WARs portlet broken after a redeploy using CLI
> ------------------------------------------------------
>
> Key: GERONIMO-1974
> URL: http://issues.apache.org/jira/browse/GERONIMO-1974
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: console
> Versions: 1.1
> Reporter: Prasad Kashyap
> Assignee: Aaron Mulder
> Priority: Blocker
> Fix For: 1.1
> Attachments: redeploy-stacktrace.txt
>
> After a redeploy is done by CLI, the portlet in the console that displays the list is broken.
> (http://localhost:8080/console/portal/apps/apps_war). It shows the message, "Error occurred in portlet!" . It needs a server restart to fix this problem. Stacktrace attached.
--
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-1974) Can't "redeploy" a copy of an
application using a different version in the module ID
Posted by "Prasad Kashyap (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1974?page=comments#action_12379113 ]
Prasad Kashyap commented on GERONIMO-1974:
------------------------------------------
When a newer version of the module is redeployed, the configuration of the newer module is marked as load=false, even though the configuration it is replacing is not marked such.
1) unpacked server.
2) redeployed welcome-jetty version 1.2 (by changing version number in plan to 1.2)
3) config.xml contains welcome-jetty 1.2 configuration now. (good)
4) welcome-jetty/1.2/car has load="false" (???)
> Can't "redeploy" a copy of an application using a different version in the module ID
> ------------------------------------------------------------------------------------
>
> Key: GERONIMO-1974
> URL: http://issues.apache.org/jira/browse/GERONIMO-1974
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: console
> Versions: 1.1
> Reporter: Prasad Kashyap
> Assignee: Dain Sundstrom
> Priority: Blocker
> Fix For: 1.1
> Attachments: 1974-redeploy-improvements.patch, redeploy-stacktrace.txt
>
> If you deploy an application with version foo/bar/1.0/baz and then change the plan to be foo/bar/1.1/baz and try to redeploy it doesn't work.
--
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-1974) Listing WARs portlet broken after a
redeploy using CLI
Posted by "Prasad Kashyap (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1974?page=all ]
Prasad Kashyap updated GERONIMO-1974:
-------------------------------------
Attachment: redeploy-stacktrace.txt
> Listing WARs portlet broken after a redeploy using CLI
> ------------------------------------------------------
>
> Key: GERONIMO-1974
> URL: http://issues.apache.org/jira/browse/GERONIMO-1974
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: console
> Versions: 1.1
> Reporter: Prasad Kashyap
> Assignee: Aaron Mulder
> Priority: Blocker
> Fix For: 1.1
> Attachments: redeploy-stacktrace.txt
>
> After a redeploy is done by CLI, the portlet in the console that displays the list is broken.
> (http://localhost:8080/console/portal/apps/apps_war). It shows the message, "Error occurred in portlet!" . It needs a server restart to fix this problem. Stacktrace attached.
--
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-1974) Can't "redeploy" a copy of an
application using a different version in the module ID
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1974?page=comments#action_12378253 ]
Aaron Mulder commented on GERONIMO-1974:
----------------------------------------
Another bug releated to this issue -- when you redeploy to get a new version, the config.xml keeps the original version, so the server fails on restart.
A feature was added to the attribute manager to migrate settings to a newer version -- we need to call this from the configuration manager.
> Can't "redeploy" a copy of an application using a different version in the module ID
> ------------------------------------------------------------------------------------
>
> Key: GERONIMO-1974
> URL: http://issues.apache.org/jira/browse/GERONIMO-1974
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: console
> Versions: 1.1
> Reporter: Prasad Kashyap
> Assignee: Dain Sundstrom
> Priority: Blocker
> Fix For: 1.1
> Attachments: 1974-redeploy-improvements.patch, redeploy-stacktrace.txt
>
> If you deploy an application with version foo/bar/1.0/baz and then change the plan to be foo/bar/1.1/baz and try to redeploy it doesn't work.
--
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-1974) Can't "redeploy" a copy of an
application using a different version in the module ID
Posted by "Prasad Kashyap (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1974?page=comments#action_12377953 ]
Prasad Kashyap commented on GERONIMO-1974:
------------------------------------------
This is how I think the redeploy should work.
I don't mind if, by default, it replaces the target module entirely, in the config.xml and in the repo but the redeploy should have an option of leaving them behind, running.
So if during redeploy, the "co-exist" option is chosen, the earlier version of the target module should be left behind running. The configirations should still be loaded and the files in the repo left behind.
However, the latest version of the app serves requests.
The user now the option of removing earlier version(s) when he is satisfied the latest version is working as desired.
The multiple versions of the app introduce layers of redundancy such that if the latest version goes down/stops, the immediate earlier version takes over as the backup.
It worked like this by default until y'day.
> Can't "redeploy" a copy of an application using a different version in the module ID
> ------------------------------------------------------------------------------------
>
> Key: GERONIMO-1974
> URL: http://issues.apache.org/jira/browse/GERONIMO-1974
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: console
> Versions: 1.1
> Reporter: Prasad Kashyap
> Assignee: Aaron Mulder
> Priority: Blocker
> Fix For: 1.1
> Attachments: redeploy-stacktrace.txt
>
> If you deploy an application with version foo/bar/1.0/baz and then change the plan to be foo/bar/1.1/baz and try to redeploy it doesn't work.
--
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-1974) Listing WARs portlet broken after
a redeploy using CLI
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1974?page=comments#action_12377943 ]
Aaron Mulder commented on GERONIMO-1974:
----------------------------------------
1) I wouldn't expect you to be able to deploy an application with a 1.2 deployment plan on 1.1. So it doesn't bother me that the deployment isn't successful.
2) We probably still shouldn't blow up. Please post the WAR and plan you're using to this JIRA so we can try to produce a better error message like "deployment failed due to invalid deployment plan format" or whatever.
> Listing WARs portlet broken after a redeploy using CLI
> ------------------------------------------------------
>
> Key: GERONIMO-1974
> URL: http://issues.apache.org/jira/browse/GERONIMO-1974
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: console
> Versions: 1.1
> Reporter: Prasad Kashyap
> Assignee: Aaron Mulder
> Priority: Blocker
> Fix For: 1.1
> Attachments: redeploy-stacktrace.txt
>
> After a redeploy is done by CLI, the portlet in the console that displays the list is broken.
> (http://localhost:8080/console/portal/apps/apps_war). It shows the message, "Error occurred in portlet!" . It needs a server restart to fix this problem. Stacktrace attached.
--
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-1974) Can't "redeploy" a copy of an
application using a different version in the module ID
Posted by "Prasad Kashyap (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1974?page=comments#action_12377948 ]
Prasad Kashyap commented on GERONIMO-1974:
------------------------------------------
Aaron, this new title and description sounds good.
But I still have the problem with the error message on the portlet. http://localhost:8080/console/portal/apps/apps_war.
> Can't "redeploy" a copy of an application using a different version in the module ID
> ------------------------------------------------------------------------------------
>
> Key: GERONIMO-1974
> URL: http://issues.apache.org/jira/browse/GERONIMO-1974
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: console
> Versions: 1.1
> Reporter: Prasad Kashyap
> Assignee: Aaron Mulder
> Priority: Blocker
> Fix For: 1.1
> Attachments: redeploy-stacktrace.txt
>
> If you deploy an application with version foo/bar/1.0/baz and then change the plan to be foo/bar/1.1/baz and try to redeploy it doesn't work.
--
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-1974) Can't "redeploy" a copy of an
application using a different version in the module ID
Posted by "Dain Sundstrom (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1974?page=all ]
Dain Sundstrom closed GERONIMO-1974:
------------------------------------
Resolution: Fixed
Added call to load(artifact) which marks the new configuration as load (it existed but wasn't marked as loaded). Also add a hook to migrate configuration settings on redeploy.
> Can't "redeploy" a copy of an application using a different version in the module ID
> ------------------------------------------------------------------------------------
>
> Key: GERONIMO-1974
> URL: http://issues.apache.org/jira/browse/GERONIMO-1974
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: console
> Versions: 1.1
> Reporter: Prasad Kashyap
> Assignee: Dain Sundstrom
> Priority: Blocker
> Fix For: 1.1
> Attachments: 1974-redeploy-improvements.patch, redeploy-stacktrace.txt
>
> If you deploy an application with version foo/bar/1.0/baz and then change the plan to be foo/bar/1.1/baz and try to redeploy it doesn't work.
--
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-1974) Can't "redeploy" a copy of an
application using a different version in the module ID
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1974?page=all ]
Aaron Mulder reassigned GERONIMO-1974:
--------------------------------------
Assign To: Dain Sundstrom (was: Aaron Mulder)
> Can't "redeploy" a copy of an application using a different version in the module ID
> ------------------------------------------------------------------------------------
>
> Key: GERONIMO-1974
> URL: http://issues.apache.org/jira/browse/GERONIMO-1974
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: console
> Versions: 1.1
> Reporter: Prasad Kashyap
> Assignee: Dain Sundstrom
> Priority: Blocker
> Fix For: 1.1
> Attachments: 1974-redeploy-improvements.patch, redeploy-stacktrace.txt
>
> If you deploy an application with version foo/bar/1.0/baz and then change the plan to be foo/bar/1.1/baz and try to redeploy it doesn't work.
--
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-1974) Can't "redeploy" a copy of an
application using a different version in the module ID
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1974?page=all ]
Aaron Mulder updated GERONIMO-1974:
-----------------------------------
Attachment: 1974-redeploy-improvements.patch
Here's the work in progress. It fixes most of the problems, except there's still a lingering problem with redeploying a stopped configuration. It looks like in thet scenario, the new configuration is loaded but not started, but the ConfigurationStatus in the ConfigurationModel isn't put into the loaded state. Therefore ConfigurationManager.isLoaded returns false, but ConfigurationManager.load fails because certain GBeans already exist. In other words, the heart of the problem appears to be the ConfigurationStatus being out of sync with the actual status of the configuration.
Dain, if you can review the changes to SimpleConfigurationManager and look into this last remaining issue, that would be great.
To reproduce, apply the patch, build, and make a symlink "jetty" from the Geronimo tree to the assembly output and run this sequence:
java -jar jetty/bin/deployer.jar --verbose undeploy welcome-jetty
java -jar jetty/bin/deployer.jar --verbose deploy applications/welcome/target/geronimo-welcome-1.1-SNAPSHOT.war
java -jar jetty/bin/deployer.jar --verbose stop geronimo-welcome-1.1-SNAPSHOT
java -jar jetty/bin/deployer.jar --verbose redeploy applications/welcome/target/geronimo-welcome-1.1-SNAPSHOT.war
(everything up to here appears to work OK)
java -jar jetty/bin/deployer.jar --verbose start geronimo-welcome-1.1-SNAPSHOT
java -jar jetty/bin/deployer.jar --verbose stop geronimo-welcome-1.1-SNAPSHOT
java -jar jetty/bin/deployer.jar --verbose start geronimo-welcome-1.1-SNAPSHOT
The start commands either fail or say the module is already running, and the stop commands do nothing, but list-modules never shows it as running. Starting from the console blows up with the stack trace shown below. The web URL http://localhost:8080/geronimo-welcome-1.1-SNAPSHOT/ never shows anything.
Redeploy seems to work OK if the original module was running, regardless of whether it had a module ID with a version and whether you changed the version if it had one.
org.apache.geronimo.kernel.config.LifecycleException: load of default/geronimo-welcome-1.1-SNAPSHOT/1146848427688/war failed
at org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:300)
at org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:253)
at org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:228)
at org.apache.geronimo.kernel.config.KernelConfigurationManager.loadConfiguration(KernelConfigurationManager.java:110)
...
Caused by: org.apache.geronimo.kernel.GBeanAlreadyExistsException: GBean already registered: geronimo.config:name="default/geronimo-welcome-1.1-SNAPSHOT/1146848427688/war"
at org.apache.geronimo.kernel.basic.BasicRegistry.register(BasicRegistry.java:88)
at org.apache.geronimo.kernel.basic.BasicKernel.loadGBean(BasicKernel.java:355)
at org.apache.geronimo.kernel.config.KernelConfigurationManager.load(KernelConfigurationManager.java:141)
> Can't "redeploy" a copy of an application using a different version in the module ID
> ------------------------------------------------------------------------------------
>
> Key: GERONIMO-1974
> URL: http://issues.apache.org/jira/browse/GERONIMO-1974
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: console
> Versions: 1.1
> Reporter: Prasad Kashyap
> Assignee: Aaron Mulder
> Priority: Blocker
> Fix For: 1.1
> Attachments: 1974-redeploy-improvements.patch, redeploy-stacktrace.txt
>
> If you deploy an application with version foo/bar/1.0/baz and then change the plan to be foo/bar/1.1/baz and try to redeploy it doesn't work.
--
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-1974) Can't "redeploy" a copy of an
application using a different version in the module ID
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1974?page=all ]
Aaron Mulder updated GERONIMO-1974:
-----------------------------------
Summary: Can't "redeploy" a copy of an application using a different version in the module ID (was: Listing WARs portlet broken after a redeploy using CLI)
Description: If you deploy an application with version foo/bar/1.0/baz and then change the plan to be foo/bar/1.1/baz and try to redeploy it doesn't work. (was: After a redeploy is done by CLI, the portlet in the console that displays the list is broken.
(http://localhost:8080/console/portal/apps/apps_war). It shows the message, "Error occurred in portlet!" . It needs a server restart to fix this problem. Stacktrace attached.
)
> Can't "redeploy" a copy of an application using a different version in the module ID
> ------------------------------------------------------------------------------------
>
> Key: GERONIMO-1974
> URL: http://issues.apache.org/jira/browse/GERONIMO-1974
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: console
> Versions: 1.1
> Reporter: Prasad Kashyap
> Assignee: Aaron Mulder
> Priority: Blocker
> Fix For: 1.1
> Attachments: redeploy-stacktrace.txt
>
> If you deploy an application with version foo/bar/1.0/baz and then change the plan to be foo/bar/1.1/baz and try to redeploy it doesn't work.
--
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-1974) Listing WARs portlet broken after
a redeploy using CLI
Posted by "Prasad Kashyap (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1974?page=comments#action_12377947 ]
Prasad Kashyap commented on GERONIMO-1974:
------------------------------------------
I bumped the version number in our welcome-jetty plan. It's the same 1.1 plan we have.
C:\Apache\geronimo\configs\welcome-jetty\target\plan\plan.xml
I was trying to mimic a customer scenario of the customer redeploying another version of his app.
The command I used is pasted in an earlier comment.
One other thing - after redeploying 1.2 version of welcome-jetty against 1.1 version already installed, in our var/config/config.xml, the geronimo/welcome-jetty/1.1-SNAPSHOT/car is unloaded but the 1.2 is never loaded into the config file. However, the 1.2 resources are installed in the repo along with the 1.1 version resources
This worked differently yesterday. Until y'day, the files were in the repo and the latest version was loaded in the config. The earlier versions were left behind in the repo and the config.xml had the earlier version set to load=false.
> Listing WARs portlet broken after a redeploy using CLI
> ------------------------------------------------------
>
> Key: GERONIMO-1974
> URL: http://issues.apache.org/jira/browse/GERONIMO-1974
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: console
> Versions: 1.1
> Reporter: Prasad Kashyap
> Assignee: Aaron Mulder
> Priority: Blocker
> Fix For: 1.1
> Attachments: redeploy-stacktrace.txt
>
> After a redeploy is done by CLI, the portlet in the console that displays the list is broken.
> (http://localhost:8080/console/portal/apps/apps_war). It shows the message, "Error occurred in portlet!" . It needs a server restart to fix this problem. Stacktrace attached.
--
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-1974) Can't "redeploy" a copy of an
application using a different version in the module ID
Posted by "Prasad Kashyap (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1974?page=comments#action_12379119 ]
Prasad Kashyap commented on GERONIMO-1974:
------------------------------------------
In my C:\Apache\geronimo\configs\welcome-jetty\target\plan\plan.xml file, I changed the version number from 1.1 to 1.2.
Then I executed the following command -
deploy --user system --password manager redeploy C:\Apache\geronimo\applications\welcome\target\geronimo-welcome-1.1-SNAPSHOT.war C:\Apache\geronimo\configs\welcome-jetty\target\plan\plan.xml geronimo/welcome-jetty/1.1-SNAPSHOT/car
> Can't "redeploy" a copy of an application using a different version in the module ID
> ------------------------------------------------------------------------------------
>
> Key: GERONIMO-1974
> URL: http://issues.apache.org/jira/browse/GERONIMO-1974
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: console
> Versions: 1.1
> Reporter: Prasad Kashyap
> Assignee: Dain Sundstrom
> Priority: Blocker
> Fix For: 1.1
> Attachments: 1974-redeploy-improvements.patch, redeploy-stacktrace.txt
>
> If you deploy an application with version foo/bar/1.0/baz and then change the plan to be foo/bar/1.1/baz and try to redeploy it doesn't work.
--
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] Resolved: (GERONIMO-1974) Listing WARs portlet broken after
a redeploy using CLI
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1974?page=all ]
Aaron Mulder resolved GERONIMO-1974:
------------------------------------
Resolution: Cannot Reproduce
Tried:
- go to WAR list in console
- java -jar bin/deployer.jar redeploy (welcome WAR) (welcome WAR plan)
- reload WAR list in console
No errors.
If this is still a problem, please attach a WAR file and specific instructions and reopen this issue.
> Listing WARs portlet broken after a redeploy using CLI
> ------------------------------------------------------
>
> Key: GERONIMO-1974
> URL: http://issues.apache.org/jira/browse/GERONIMO-1974
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: console
> Versions: 1.1
> Reporter: Prasad Kashyap
> Assignee: Aaron Mulder
> Priority: Blocker
> Fix For: 1.1
> Attachments: redeploy-stacktrace.txt
>
> After a redeploy is done by CLI, the portlet in the console that displays the list is broken.
> (http://localhost:8080/console/portal/apps/apps_war). It shows the message, "Error occurred in portlet!" . It needs a server restart to fix this problem. Stacktrace attached.
--
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