[ 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
