geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jürgen Weber (JIRA) <j...@apache.org>
Subject [jira] Created: (GERONIMO-4305) PortletException with Redeploy application checked for non existent application
Date Tue, 16 Sep 2008 06:01:46 GMT
PortletException with Redeploy application checked for non existent application
-------------------------------------------------------------------------------

                 Key: GERONIMO-4305
                 URL: https://issues.apache.org/jira/browse/GERONIMO-4305
             Project: Geronimo
          Issue Type: Bug
      Security Level: public (Regular issues)
          Components: deployment
    Affects Versions: 2.1.3
            Reporter: Jürgen Weber
            Priority: Minor


If you deploy an application, have "Redeploy application" checked, but the application does
not exist, there is a PortletException.

This does not look very professional, Geronimo should instead handle gracefully the situation.

HTTP ERROR: 500

INTERNAL_SERVER_ERROR

RequestURI=/console/portal//Applications/Deploy%20New/__ac0x3plugin0x2Deployment!227983155|0
Caused by:

javax.portlet.PortletException
	at org.apache.geronimo.console.configmanager.DeploymentPortlet.processAction(DeploymentPortlet.java:224)


Caused by: javax.portlet.PortletException: jWhichJSP does not appear to be a the name of a
module available on the selected server. Perhaps it has already been stopped or undeployed?
 If you're trying to specify a TargetModuleID, use the syntax TargetName|ModuleName instead.
If you're not sure what's running, try the list-modules command.
	at org.apache.geronimo.console.configmanager.DeploymentPortlet.identifyTargets(DeploymentPortlet.java:254)
	at org.apache.geronimo.console.configmanager.DeploymentPortlet.processAction(DeploymentPortlet.java:142)
	... 57 more
Caused by: org.apache.geronimo.common.DeploymentException: jWhichJSP does not appear to be
a the name of a module available on the selected server. Perhaps it has already been stopped
or undeployed?  If you're trying to specify a TargetModuleID, use the syntax TargetName|ModuleName
instead. If you're not sure what's running, try the list-modules command.
	at org.apache.geronimo.deployment.plugin.ConfigIDExtractor.identifyTargetModuleIDs(ConfigIDExtractor.java:205)
	at org.apache.geronimo.console.configmanager.DeploymentPortlet.identifyTargets(DeploymentPortlet.java:242)
	... 58 more

Nested Exception is javax.portlet.PortletException: jWhichJSP does not appear to be a the
name of a module available on the selected server. Perhaps it has already been stopped or
undeployed?  If you're trying to specify a TargetModuleID, use the syntax TargetName|ModuleName
instead. If you're not sure what's running, try the list-modules command.
	at org.apache.geronimo.console.configmanager.DeploymentPortlet.identifyTargets(DeploymentPortlet.java:254)
	at org.apache.geronimo.console.configmanager.DeploymentPortlet.processAction(DeploymentPortlet.java:142)
	at org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:218)


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message