Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Message-ID: <12333503.1148450110298.JavaMail.jira@brutus>
Date: Wed, 24 May 2006 05:55:10 +0000 (GMT+00:00)
From: "Kevan Miller (JIRA)" <dev@geronimo.apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Reopened: (GERONIMO-2006) Deploying an application with an
 incorrect deployment plan results in non-functional admin console panel
In-Reply-To: <32593964.1147290064534.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ 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