You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Rex Wang (JIRA)" <ji...@apache.org> on 2009/05/20 05:38:45 UTC
[jira] Commented: (GERONIMO-4305) PortletException with Redeploy
application checked for non existent application
[ https://issues.apache.org/jira/browse/GERONIMO-4305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12710989#action_12710989 ]
Rex Wang commented on GERONIMO-4305:
------------------------------------
Besides, the two patches all resolve the http 500 error.
And the GERONIMO-4305-trunk.patch contains the properties file for globalization usage.
Anyone can help commit it?
thanks
-Rex
> 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, 2.1.4
> Reporter: Jürgen Weber
> Assignee: Rex Wang
> Priority: Minor
> Fix For: 2.2
>
> Attachments: GERONIMO-4305-trunk.patch, GERONIMO-4305.patch
>
>
> 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.