geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Colasurdo (JIRA)" <...@geronimo.apache.org>
Subject [jira] Commented: (GERONIMO-2006) Deploying an application with an incorrect deployment plan results in non-functional admin console panel
Date Mon, 15 May 2006 20:17:12 GMT
    [ 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


Mime
View raw message