[jira] Updated: (GERONIMO-2006) Deploying an application with an incorrect deployment plan results in non-functional admin console panel
[ 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
[ 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] Updated: (GERONIMO-2006) Deploying an application with an incorrect deployment plan results in non-functional admin console panel
[ 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
[ 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] Updated: (GERONIMO-2006) Deploying an application with an incorrect deployment plan results in non-functional admin console panel
[ 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] Updated: (GERONIMO-2006) Deploying an application with an incorrect deployment plan results in non-functional admin console panel
[ 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
[ 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
