You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Dave Colasurdo (JIRA)" <de...@geronimo.apache.org> on 2006/05/10 21:41:04 UTC
[jira] Created: (GERONIMO-2006) Deploying an application with an
incorrect depolyment plan results in non-functional admin console panel
Deploying an application with an incorrect depolyment plan results in non-functional admin console panel
--------------------------------------------------------------------------------------------------------
Key: GERONIMO-2006
URL: http://issues.apache.org/jira/browse/GERONIMO-2006
Project: Geronimo
Type: Bug
Security: public (Regular issues)
Components: console
Versions: 1.1
Reporter: Dave Colasurdo
Deploying myApp.war using badPlan.xml (both attached) results in a non-functioning "Show Web App Wars" panel.
The console "Deploy Applications" panel reports "application installed and started successfully". However, the application did not startup succesfully. The badPlan file is actually missing tcpListenerAddress=auto which causes TomcatReceiver Gbean to fail startup. I've attached the stacktrace to the JIRA.
>From then on, the "Web App Wars" console panel shows "portlet error" and there is no way to uninstall the bad application via the console. The server must be stopped and restarted in order to have the "Web App War" panel function correctly.
The console should be able to report the true status of the "deploy/start" and recover from deploying a bad plan.
--
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-2006) Deploying an application with an
incorrect deployment plan results in non-functional admin console panel
Posted by "Paul McMahan (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2006?page=all ]
Paul McMahan updated GERONIMO-2006:
-----------------------------------
Patch Info: [Patch Available]
> Deploying an application with an incorrect deployment plan results in non-functional admin console panel
> --------------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-2006
> URL: http://issues.apache.org/jira/browse/GERONIMO-2006
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: deployment, console
> Versions: 1.1
> Reporter: Dave Colasurdo
> Assignee: Aaron Mulder
> Priority: Blocker
> Fix For: 1.1
> Attachments: GERONIMO-2006.patch, Myapp.war, badPlan.xml, badPlan2.xml, deployment_portlet.jpg, stackTrace.log
>
> Deploying myApp.war using badPlan.xml (both attached) results in a non-functioning "Show Web App Wars" panel.
> The console "Deploy Applications" panel reports "application installed and started successfully". However, the application did not startup succesfully. The badPlan file is actually missing tcpListenerAddress=auto which causes TomcatReceiver Gbean to fail startup. I've attached the stacktrace to the JIRA.
> From then on, the "Web App Wars" console panel shows "portlet error" and there is no way to uninstall the bad application via the console. The server must be stopped and restarted in order to have the "Web App War" panel function correctly.
> The console should be able to report the true status of the "deploy/start" and recover from deploying a bad plan.
--
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-2006) Deploying an application with an
incorrect deployment plan results in non-functional admin console panel
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2006?page=comments#action_12413071 ]
David Jencks commented on GERONIMO-2006:
----------------------------------------
Since it was already on my machine I added and committed the missing portlet in rev 409080. I'll leave it open in case I missed anything else.
> Deploying an application with an incorrect deployment plan results in non-functional admin console panel
> --------------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-2006
> URL: http://issues.apache.org/jira/browse/GERONIMO-2006
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: deployment, console
> Versions: 1.1
> Reporter: Dave Colasurdo
> Assignee: Kevan Miller
> Priority: Blocker
> Fix For: 1.1
> Attachments: GERONIMO-2006.patch, Myapp.war, badPlan.xml, badPlan.xml, badPlan2.xml, deployment_portlet.jpg, stackTrace.log
>
> Deploying myApp.war using badPlan.xml (both attached) results in a non-functioning "Show Web App Wars" panel.
> The console "Deploy Applications" panel reports "application installed and started successfully". However, the application did not startup succesfully. The badPlan file is actually missing tcpListenerAddress=auto which causes TomcatReceiver Gbean to fail startup. I've attached the stacktrace to the JIRA.
> From then on, the "Web App Wars" console panel shows "portlet error" and there is no way to uninstall the bad application via the console. The server must be stopped and restarted in order to have the "Web App War" panel function correctly.
> The console should be able to report the true status of the "deploy/start" and recover from deploying a bad plan.
--
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-2006) Deploying an application with an
incorrect deployment plan results in non-functional admin console panel
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2006?page=comments#action_12407160 ]
Aaron Mulder commented on GERONIMO-2006:
----------------------------------------
Fixed so Jetty deployer barfs on plans with the Tomcat namespace and vice versa.
Still need to fix the console to show deployment errors.
> Deploying an application with an incorrect deployment plan results in non-functional admin console panel
> --------------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-2006
> URL: http://issues.apache.org/jira/browse/GERONIMO-2006
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: deployment, console
> Versions: 1.1
> Reporter: Dave Colasurdo
> Assignee: Aaron Mulder
> Priority: Blocker
> Fix For: 1.1
> Attachments: Myapp.war, badPlan.xml, badPlan2.xml, stackTrace.log
>
> Deploying myApp.war using badPlan.xml (both attached) results in a non-functioning "Show Web App Wars" panel.
> The console "Deploy Applications" panel reports "application installed and started successfully". However, the application did not startup succesfully. The badPlan file is actually missing tcpListenerAddress=auto which causes TomcatReceiver Gbean to fail startup. I've attached the stacktrace to the JIRA.
> From then on, the "Web App Wars" console panel shows "portlet error" and there is no way to uninstall the bad application via the console. The server must be stopped and restarted in order to have the "Web App War" panel function correctly.
> The console should be able to report the true status of the "deploy/start" and recover from deploying a bad plan.
--
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-2006) Deploying an application with an
incorrect deployment plan results in non-functional admin console panel
Posted by "Dave Colasurdo (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2006?page=all ]
Dave Colasurdo updated GERONIMO-2006:
-------------------------------------
Summary: Deploying an application with an incorrect deployment plan results in non-functional admin console panel (was: Deploying an application with an incorrect depolyment plan results in non-functional admin console panel)
> Deploying an application with an incorrect deployment plan results in non-functional admin console panel
> --------------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-2006
> URL: http://issues.apache.org/jira/browse/GERONIMO-2006
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: console
> Versions: 1.1
> Reporter: Dave Colasurdo
> Attachments: Myapp.war, badPlan.xml, badPlan2.xml, stackTrace.log
>
> Deploying myApp.war using badPlan.xml (both attached) results in a non-functioning "Show Web App Wars" panel.
> The console "Deploy Applications" panel reports "application installed and started successfully". However, the application did not startup succesfully. The badPlan file is actually missing tcpListenerAddress=auto which causes TomcatReceiver Gbean to fail startup. I've attached the stacktrace to the JIRA.
> From then on, the "Web App Wars" console panel shows "portlet error" and there is no way to uninstall the bad application via the console. The server must be stopped and restarted in order to have the "Web App War" panel function correctly.
> The console should be able to report the true status of the "deploy/start" and recover from deploying a bad plan.
--
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-2006) Deploying an application with an
incorrect depolyment plan results in non-functional admin console panel
Posted by "Dave Colasurdo (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2006?page=all ]
Dave Colasurdo updated GERONIMO-2006:
-------------------------------------
Attachment: stackTrace.log
badPlan.xml
Myapp.war
> Deploying an application with an incorrect depolyment plan results in non-functional admin console panel
> --------------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-2006
> URL: http://issues.apache.org/jira/browse/GERONIMO-2006
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: console
> Versions: 1.1
> Reporter: Dave Colasurdo
> Attachments: Myapp.war, badPlan.xml, stackTrace.log
>
> Deploying myApp.war using badPlan.xml (both attached) results in a non-functioning "Show Web App Wars" panel.
> The console "Deploy Applications" panel reports "application installed and started successfully". However, the application did not startup succesfully. The badPlan file is actually missing tcpListenerAddress=auto which causes TomcatReceiver Gbean to fail startup. I've attached the stacktrace to the JIRA.
> From then on, the "Web App Wars" console panel shows "portlet error" and there is no way to uninstall the bad application via the console. The server must be stopped and restarted in order to have the "Web App War" panel function correctly.
> The console should be able to report the true status of the "deploy/start" and recover from deploying a bad plan.
--
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-2006) Deploying an application with an
incorrect deployment plan results in non-functional admin console panel
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2006?page=comments#action_12402473 ]
Aaron Mulder commented on GERONIMO-2006:
----------------------------------------
Some recent changes most likely affected this.
It should now always be possible to undeploy after a failed deployment (e.g., when the GBean fails to start). I'm glad to hear that the console WAR doesn't break, though I don't recall exactly what caused that.
As a side note, the deployment should not succeed (and should get different exceptions) on Jetty, since it uses a Tomcat namespace.
I think the remaining issues are:
- console should show all error messages when a deployment fails
- Jetty deployer should immediately reject any deployment with a Tomcat plan and vice versa
> Deploying an application with an incorrect deployment plan results in non-functional admin console panel
> --------------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-2006
> URL: http://issues.apache.org/jira/browse/GERONIMO-2006
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: deployment, console
> Versions: 1.1
> Reporter: Dave Colasurdo
> Assignee: Aaron Mulder
> Priority: Blocker
> Fix For: 1.1
> Attachments: Myapp.war, badPlan.xml, badPlan2.xml, stackTrace.log
>
> Deploying myApp.war using badPlan.xml (both attached) results in a non-functioning "Show Web App Wars" panel.
> The console "Deploy Applications" panel reports "application installed and started successfully". However, the application did not startup succesfully. The badPlan file is actually missing tcpListenerAddress=auto which causes TomcatReceiver Gbean to fail startup. I've attached the stacktrace to the JIRA.
> From then on, the "Web App Wars" console panel shows "portlet error" and there is no way to uninstall the bad application via the console. The server must be stopped and restarted in order to have the "Web App War" panel function correctly.
> The console should be able to report the true status of the "deploy/start" and recover from deploying a bad plan.
--
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-2006) Deploying an application with an
incorrect deployment plan results in non-functional admin console panel
Posted by "Erin Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2006?page=comments#action_12402402 ]
Erin Mulder commented on GERONIMO-2006:
---------------------------------------
BTW, despite the various critical errors I encoutered while trying to reproduce this, I was not able to break the webapp portlet. It worked fine throughout.
> Deploying an application with an incorrect deployment plan results in non-functional admin console panel
> --------------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-2006
> URL: http://issues.apache.org/jira/browse/GERONIMO-2006
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: deployment, console
> Versions: 1.1
> Reporter: Dave Colasurdo
> Assignee: Aaron Mulder
> Priority: Blocker
> Fix For: 1.1
> Attachments: Myapp.war, badPlan.xml, badPlan2.xml, stackTrace.log
>
> Deploying myApp.war using badPlan.xml (both attached) results in a non-functioning "Show Web App Wars" panel.
> The console "Deploy Applications" panel reports "application installed and started successfully". However, the application did not startup succesfully. The badPlan file is actually missing tcpListenerAddress=auto which causes TomcatReceiver Gbean to fail startup. I've attached the stacktrace to the JIRA.
> From then on, the "Web App Wars" console panel shows "portlet error" and there is no way to uninstall the bad application via the console. The server must be stopped and restarted in order to have the "Web App War" panel function correctly.
> The console should be able to report the true status of the "deploy/start" and recover from deploying a bad plan.
--
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-2006) Deploying an application with an
incorrect deployment plan results in non-functional admin console panel
Posted by "Paul McMahan (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2006?page=all ]
Paul McMahan updated GERONIMO-2006:
-----------------------------------
Attachment: deployment_portlet.jpg
attaching screenshot of deployment portlet shown providing an upgraded plan
> Deploying an application with an incorrect deployment plan results in non-functional admin console panel
> --------------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-2006
> URL: http://issues.apache.org/jira/browse/GERONIMO-2006
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: deployment, console
> Versions: 1.1
> Reporter: Dave Colasurdo
> Assignee: Aaron Mulder
> Priority: Blocker
> Fix For: 1.1
> Attachments: GERONIMO-2006.patch, Myapp.war, badPlan.xml, badPlan2.xml, deployment_portlet.jpg, stackTrace.log
>
> Deploying myApp.war using badPlan.xml (both attached) results in a non-functioning "Show Web App Wars" panel.
> The console "Deploy Applications" panel reports "application installed and started successfully". However, the application did not startup succesfully. The badPlan file is actually missing tcpListenerAddress=auto which causes TomcatReceiver Gbean to fail startup. I've attached the stacktrace to the JIRA.
> From then on, the "Web App Wars" console panel shows "portlet error" and there is no way to uninstall the bad application via the console. The server must be stopped and restarted in order to have the "Web App War" panel function correctly.
> The console should be able to report the true status of the "deploy/start" and recover from deploying a bad plan.
--
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-2006) Deploying an application with an
incorrect deployment plan results in non-functional admin console panel
Posted by "Dave Colasurdo (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2006?page=comments#action_12402408 ]
Dave Colasurdo commented on GERONIMO-2006:
------------------------------------------
Thanks for looking at this issue..
I originally created the pblm on a build that was done just prior to the cut-over to moduleId. So the original reported failures weren't related to configId -vs- moduleId.. though that pblm is also worth investigation.
Concerning the non-functioning "web app WARs" panel .. The failure was pretty solid.. Perhaps this has gone away. I will try to recreate after getting a clean build. Though may be a bit delayed as I have been encountering connection errors ( svn: PROPFIND of '/openejb/branches/v2_1/openejb2': could not connect to server (https://svn.codehaus.org)) with maven m:fresh-checkout all day :(
-Dave-
> Deploying an application with an incorrect deployment plan results in non-functional admin console panel
> --------------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-2006
> URL: http://issues.apache.org/jira/browse/GERONIMO-2006
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: deployment, console
> Versions: 1.1
> Reporter: Dave Colasurdo
> Assignee: Aaron Mulder
> Priority: Blocker
> Fix For: 1.1
> Attachments: Myapp.war, badPlan.xml, badPlan2.xml, stackTrace.log
>
> Deploying myApp.war using badPlan.xml (both attached) results in a non-functioning "Show Web App Wars" panel.
> The console "Deploy Applications" panel reports "application installed and started successfully". However, the application did not startup succesfully. The badPlan file is actually missing tcpListenerAddress=auto which causes TomcatReceiver Gbean to fail startup. I've attached the stacktrace to the JIRA.
> From then on, the "Web App Wars" console panel shows "portlet error" and there is no way to uninstall the bad application via the console. The server must be stopped and restarted in order to have the "Web App War" panel function correctly.
> The console should be able to report the true status of the "deploy/start" and recover from deploying a bad plan.
--
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-2006) Deploying an application with an
incorrect depolyment plan results in non-functional admin console panel
Posted by "Dave Colasurdo (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2006?page=all ]
Dave Colasurdo updated GERONIMO-2006:
-------------------------------------
Attachment: badPlan2.xml
Here is another bad plan (badPlan2) that results in a slightly different error (i.e the deploy panel doesn't refresh and returns a blank page).
> Deploying an application with an incorrect depolyment plan results in non-functional admin console panel
> --------------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-2006
> URL: http://issues.apache.org/jira/browse/GERONIMO-2006
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: console
> Versions: 1.1
> Reporter: Dave Colasurdo
> Attachments: Myapp.war, badPlan.xml, badPlan2.xml, stackTrace.log
>
> Deploying myApp.war using badPlan.xml (both attached) results in a non-functioning "Show Web App Wars" panel.
> The console "Deploy Applications" panel reports "application installed and started successfully". However, the application did not startup succesfully. The badPlan file is actually missing tcpListenerAddress=auto which causes TomcatReceiver Gbean to fail startup. I've attached the stacktrace to the JIRA.
> From then on, the "Web App Wars" console panel shows "portlet error" and there is no way to uninstall the bad application via the console. The server must be stopped and restarted in order to have the "Web App War" panel function correctly.
> The console should be able to report the true status of the "deploy/start" and recover from deploying a bad plan.
--
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-2006) Deploying an application with an
incorrect deployment plan results in non-functional admin console panel
Posted by "Kevan Miller (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2006?page=all ]
Kevan Miller closed GERONIMO-2006:
----------------------------------
Resolution: Fixed
david jencks committed PlanExportServlet
> Deploying an application with an incorrect deployment plan results in non-functional admin console panel
> --------------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-2006
> URL: http://issues.apache.org/jira/browse/GERONIMO-2006
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: deployment, console
> Versions: 1.1
> Reporter: Dave Colasurdo
> Assignee: Kevan Miller
> Priority: Blocker
> Fix For: 1.1
> Attachments: GERONIMO-2006.patch, Myapp.war, badPlan.xml, badPlan.xml, badPlan2.xml, deployment_portlet.jpg, stackTrace.log
>
> Deploying myApp.war using badPlan.xml (both attached) results in a non-functioning "Show Web App Wars" panel.
> The console "Deploy Applications" panel reports "application installed and started successfully". However, the application did not startup succesfully. The badPlan file is actually missing tcpListenerAddress=auto which causes TomcatReceiver Gbean to fail startup. I've attached the stacktrace to the JIRA.
> From then on, the "Web App Wars" console panel shows "portlet error" and there is no way to uninstall the bad application via the console. The server must be stopped and restarted in order to have the "Web App War" panel function correctly.
> The console should be able to report the true status of the "deploy/start" and recover from deploying a bad plan.
--
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-2006) Deploying an application with an
incorrect deployment plan results in non-functional admin console panel
Posted by "Kevan Miller (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2006?page=all ]
Kevan Miller reopened GERONIMO-2006:
------------------------------------
Assign To: Kevan Miller (was: David Jencks)
The commit associated with this defect was incomplete. It was missing PlanExportServlet.
As any new function contained in PlanExportServlet has already been voted on and IMO falls under the bug-fix category. I'm following the CTR process...
> Deploying an application with an incorrect deployment plan results in non-functional admin console panel
> --------------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-2006
> URL: http://issues.apache.org/jira/browse/GERONIMO-2006
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: deployment, console
> Versions: 1.1
> Reporter: Dave Colasurdo
> Assignee: Kevan Miller
> Priority: Blocker
> Fix For: 1.1
> Attachments: GERONIMO-2006.patch, Myapp.war, badPlan.xml, badPlan.xml, badPlan2.xml, deployment_portlet.jpg, stackTrace.log
>
> Deploying myApp.war using badPlan.xml (both attached) results in a non-functioning "Show Web App Wars" panel.
> The console "Deploy Applications" panel reports "application installed and started successfully". However, the application did not startup succesfully. The badPlan file is actually missing tcpListenerAddress=auto which causes TomcatReceiver Gbean to fail startup. I've attached the stacktrace to the JIRA.
> From then on, the "Web App Wars" console panel shows "portlet error" and there is no way to uninstall the bad application via the console. The server must be stopped and restarted in order to have the "Web App War" panel function correctly.
> The console should be able to report the true status of the "deploy/start" and recover from deploying a bad plan.
--
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-2006) Deploying an application with an
incorrect deployment plan results in non-functional admin console panel
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2006?page=all ]
David Jencks updated GERONIMO-2006:
-----------------------------------
Attachment: badPlan.xml
Updated badPlan.xml with configId >> moduleId change and context-priority-classloader removed.
> Deploying an application with an incorrect deployment plan results in non-functional admin console panel
> --------------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-2006
> URL: http://issues.apache.org/jira/browse/GERONIMO-2006
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: deployment, console
> Versions: 1.1
> Reporter: Dave Colasurdo
> Assignee: Aaron Mulder
> Priority: Blocker
> Fix For: 1.1
> Attachments: GERONIMO-2006.patch, Myapp.war, badPlan.xml, badPlan.xml, badPlan2.xml, deployment_portlet.jpg, stackTrace.log
>
> Deploying myApp.war using badPlan.xml (both attached) results in a non-functioning "Show Web App Wars" panel.
> The console "Deploy Applications" panel reports "application installed and started successfully". However, the application did not startup succesfully. The badPlan file is actually missing tcpListenerAddress=auto which causes TomcatReceiver Gbean to fail startup. I've attached the stacktrace to the JIRA.
> From then on, the "Web App Wars" console panel shows "portlet error" and there is no way to uninstall the bad application via the console. The server must be stopped and restarted in order to have the "Web App War" panel function correctly.
> The console should be able to report the true status of the "deploy/start" and recover from deploying a bad plan.
--
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-2006) Deploying an application with an
incorrect deployment plan results in non-functional admin console panel
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2006?page=all ]
Aaron Mulder updated GERONIMO-2006:
-----------------------------------
Component: deployment
Priority: Blocker (was: Major)
> Deploying an application with an incorrect deployment plan results in non-functional admin console panel
> --------------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-2006
> URL: http://issues.apache.org/jira/browse/GERONIMO-2006
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: deployment, console
> Versions: 1.1
> Reporter: Dave Colasurdo
> Assignee: Aaron Mulder
> Priority: Blocker
> Fix For: 1.1
> Attachments: Myapp.war, badPlan.xml, badPlan2.xml, stackTrace.log
>
> Deploying myApp.war using badPlan.xml (both attached) results in a non-functioning "Show Web App Wars" panel.
> The console "Deploy Applications" panel reports "application installed and started successfully". However, the application did not startup succesfully. The badPlan file is actually missing tcpListenerAddress=auto which causes TomcatReceiver Gbean to fail startup. I've attached the stacktrace to the JIRA.
> From then on, the "Web App Wars" console panel shows "portlet error" and there is no way to uninstall the bad application via the console. The server must be stopped and restarted in order to have the "Web App War" panel function correctly.
> The console should be able to report the true status of the "deploy/start" and recover from deploying a bad plan.
--
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-2006) Deploying an application with an
incorrect deployment plan results in non-functional admin console panel
Posted by "Paul McMahan (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2006?page=all ]
Paul McMahan updated GERONIMO-2006:
-----------------------------------
Attachment: GERONIMO-2006.patch
I was able to recreate the problem on tomcat. It is caused by a buffer overrun when render parameters that are set during the processAction phase are bigger than 8k. Since the error messages from the deployers are often larger than 8k the attached patch works around the buffer overrun by saving the message in the portlet session instead.
The patch also looks for use of the configId attribute in the plan and if found uses the new upgrade utility to provide an upgraded version of the plan that the user can save locally as a starting point. In some cases (welcome app, jmx-debug app, etc) no further editing of the plan is required. The user can just save the updated plan for their 1.0 app and immediately deploy it again from the same portlet. The patch doesn't support upgrading plans that are embedded in the archive -- this is a bit more challenging but I think can be done.
And finally, since error messages from the deployers are often very, very long and contains several stack traces this patch just shows the first line of the error message in the console (which is usually sufficient) and provides a button to show the full message if the user wants all the gory details.
> Deploying an application with an incorrect deployment plan results in non-functional admin console panel
> --------------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-2006
> URL: http://issues.apache.org/jira/browse/GERONIMO-2006
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: deployment, console
> Versions: 1.1
> Reporter: Dave Colasurdo
> Assignee: Aaron Mulder
> Priority: Blocker
> Fix For: 1.1
> Attachments: GERONIMO-2006.patch, Myapp.war, badPlan.xml, badPlan2.xml, stackTrace.log
>
> Deploying myApp.war using badPlan.xml (both attached) results in a non-functioning "Show Web App Wars" panel.
> The console "Deploy Applications" panel reports "application installed and started successfully". However, the application did not startup succesfully. The badPlan file is actually missing tcpListenerAddress=auto which causes TomcatReceiver Gbean to fail startup. I've attached the stacktrace to the JIRA.
> From then on, the "Web App Wars" console panel shows "portlet error" and there is no way to uninstall the bad application via the console. The server must be stopped and restarted in order to have the "Web App War" panel function correctly.
> The console should be able to report the true status of the "deploy/start" and recover from deploying a bad plan.
--
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-2006) Deploying an application with an
incorrect deployment plan results in non-functional admin console panel
Posted by "Erin Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2006?page=all ]
Erin Mulder updated GERONIMO-2006:
----------------------------------
Fix Version: 1.1
Assign To: Aaron Mulder
While trying to reproduce this, I discovered different behavior in Tomcat vs. Jetty, and in web console vs. command-line deployer. It also seems that there are several different underlying bugs.
Tomcat, Web Console Deployer:
1. Deploying the attached files as they are (without changing configId to moduleId) caused stack trace and blank web page
2. After replacing configId with moduleId in badPlan.xml, I got messages about how the app had deployed and started successfully, despite the fact that it hadn't. However, it didn't break Web App WARs page, so I could uninstall it easily.
3. When I tried deploying it again without uninstalling first, I got a stack trace in the portlet window instead of a normal error message.
4. Deploying with badPlan2.xml caused stack trace in portlet window instead of error message, but didn't result in a deployment or half-deployment.
Jetty, Web Console Deployer
1. Deploying with badPlan.xml causes stack traces to STDOUT, but no indication of error to user. Portlet just redisplays. App is not deployed.
2. Same result after changing "configId" to "moduleId" in plan.
3. Deploying with badPlan2.xml causes stack traces to STDOUT and blank web page.
Jetty, Command-Line Deployer
1. Descriptive errors produced on all bad plans
Tomcat, Command-Line Deployer
1. badPlan.xml causes descriptive error
2. badPlan.xml with moduleId fix causes stack trace during start
3. badPlan2.xml causes descriptive error
> Deploying an application with an incorrect deployment plan results in non-functional admin console panel
> --------------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-2006
> URL: http://issues.apache.org/jira/browse/GERONIMO-2006
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: console
> Versions: 1.1
> Reporter: Dave Colasurdo
> Assignee: Aaron Mulder
> Fix For: 1.1
> Attachments: Myapp.war, badPlan.xml, badPlan2.xml, stackTrace.log
>
> Deploying myApp.war using badPlan.xml (both attached) results in a non-functioning "Show Web App Wars" panel.
> The console "Deploy Applications" panel reports "application installed and started successfully". However, the application did not startup succesfully. The badPlan file is actually missing tcpListenerAddress=auto which causes TomcatReceiver Gbean to fail startup. I've attached the stacktrace to the JIRA.
> From then on, the "Web App Wars" console panel shows "portlet error" and there is no way to uninstall the bad application via the console. The server must be stopped and restarted in order to have the "Web App War" panel function correctly.
> The console should be able to report the true status of the "deploy/start" and recover from deploying a bad plan.
--
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-2006) Deploying an application with an
incorrect deployment plan results in non-functional admin console panel
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2006?page=all ]
David Jencks closed GERONIMO-2006:
----------------------------------
Resolution: Fixed
Assign To: David Jencks (was: Aaron Mulder)
applied in rev 409023. +1 from jgenender, acabrera, gdamour, and possibly jsisson and djencks.
> Deploying an application with an incorrect deployment plan results in non-functional admin console panel
> --------------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-2006
> URL: http://issues.apache.org/jira/browse/GERONIMO-2006
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: deployment, console
> Versions: 1.1
> Reporter: Dave Colasurdo
> Assignee: David Jencks
> Priority: Blocker
> Fix For: 1.1
> Attachments: GERONIMO-2006.patch, Myapp.war, badPlan.xml, badPlan.xml, badPlan2.xml, deployment_portlet.jpg, stackTrace.log
>
> Deploying myApp.war using badPlan.xml (both attached) results in a non-functioning "Show Web App Wars" panel.
> The console "Deploy Applications" panel reports "application installed and started successfully". However, the application did not startup succesfully. The badPlan file is actually missing tcpListenerAddress=auto which causes TomcatReceiver Gbean to fail startup. I've attached the stacktrace to the JIRA.
> From then on, the "Web App Wars" console panel shows "portlet error" and there is no way to uninstall the bad application via the console. The server must be stopped and restarted in order to have the "Web App War" panel function correctly.
> The console should be able to report the true status of the "deploy/start" and recover from deploying a bad plan.
--
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