You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-dev@portals.apache.org by "Ate Douma (JIRA)" <ji...@apache.org> on 2009/01/28 00:04:59 UTC
[jira] Closed: (PLUTO-502) Portlet Loading error because cant't
find app descriptor
[ https://issues.apache.org/jira/browse/PLUTO-502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ate Douma closed PLUTO-502.
---------------------------
Resolution: Cannot Reproduce
testsuite clearly works just fine for me. I suspect a Tomcat misconfiguration must have been the cause of this.
> Portlet Loading error because cant't find app descriptor
> --------------------------------------------------------
>
> Key: PLUTO-502
> URL: https://issues.apache.org/jira/browse/PLUTO-502
> Project: Pluto
> Issue Type: Bug
> Components: portlet container
> Affects Versions: 2.0.0
> Environment: Tomcat 5.5
> Reporter: Gonzalo Aguilar
>
> Hi All!
> Pluto container does not find testsuite portlet.
> At first I thought that was something related with deployment configuration. So I made some detailed log and found that a problem with the crossContext=true switch was found in the tomcat server configuration file.
> Now it seems it does not find the portlet application descriptor. Here is the error (looks little bit modified to be able to trace without all stacktrace logging):
> INFO [http-8180-Processor25] (ExpressionEvaluatorProxy.java:54) - Attempting to utilize expression evaluator proxy 'org.apache.pluto.tags.el.JSP20ExpressionEvaluatorProxy'
> INFO [http-8180-Processor25] (ExpressionEvaluatorProxy.java:76) - ExpressionEvaluator Proxy Found: org.apache.pluto.tags.el.JSP20ExpressionEvaluatorProxy
> WARN [http-8180-Processor25] (PortletContextManager.java:243) - Unable to retrieve portlet application descriptor: '/testsuite'
> WARN [http-8180-Processor25] (PortletContextManager.java:243) - Unable to retrieve portlet application descriptor: '/testsuite'
> ERROR [http-8180-Processor25] (SupportedModesServiceImpl.java:122) - Can't get Portlet application descriptor: Unable to retrieve portlet application descriptor: '/testsuite'
> INFO [http-8180-Processor25] (SupportedModesServiceImpl.java:154) - Portlet mode 'view' not found for portletId: '/testsuite.TestPortlet1!510736053|1'
> WARN [http-8180-Processor25] (PortletContextManager.java:243) - Unable to retrieve portlet application descriptor: '/testsuite'
> ERROR [http-8180-Processor25] (SupportedModesServiceImpl.java:122) - Can't get Portlet application descriptor: Unable to retrieve portlet application descriptor: '/testsuite'
> INFO [http-8180-Processor25] (SupportedModesServiceImpl.java:154) - Portlet mode 'edit' not found for portletId: '/testsuite.TestPortlet1!510736053|1'
> WARN [http-8180-Processor25] (PortletContextManager.java:243) - Unable to retrieve portlet application descriptor: '/testsuite'
> ERROR [http-8180-Processor25] (SupportedModesServiceImpl.java:122) - Can't get Portlet application descriptor: Unable to retrieve portlet application descriptor: '/testsuite'
> INFO [http-8180-Processor25] (SupportedModesServiceImpl.java:154) - Portlet mode 'help' not found for portletId: '/testsuite.TestPortlet1!510736053|1'
> ---
> Stacktrace:
> ----
> Error rendering portlet.
> org.apache.pluto.PortletContainerException: Unable to retrieve portlet application descriptor: '/testsuite'
> at org.apache.pluto.core.PortletContextManager.getPortletApplicationDescriptor(PortletContextManager.java:244)
> at org.apache.pluto.core.PortletContainerImpl.filterInitialisation(PortletContainerImpl.java:672)
> at org.apache.pluto.core.PortletContainerImpl.doRender(PortletContainerImpl.java:222)
> at org.apache.pluto.driver.tags.PortletTag.doStartTag(PortletTag.java:152)
> at org.apache.jsp.WEB_002dINF.themes.portlet_002dskin_jsp._jspx_meth_pluto_005fportlet_005f0(portlet_002dskin_jsp.java:99)
> at org.apache.jsp.WEB_002dINF.themes.portlet_002dskin_jsp._jspService(portlet_002dskin_jsp.java:74)
> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:331)
> at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:329)
> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
> at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:691)
> at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:594)
> at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:505)
> at org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:965)
> at org.apache.jsp.WEB_002dINF.themes.pluto_002ddefault_002dtheme_jsp._jspx_meth_c_005fforEach_005f2(pluto_002ddefault_002dtheme_jsp.java:573)
> at org.apache.jsp.WEB_002dINF.themes.pluto_002ddefault_002dtheme_jsp._jspx_meth_c_005fotherwise_005f0(pluto_002ddefault_002dtheme_jsp.java:461)
> at org.apache.jsp.WEB_002dINF.themes.pluto_002ddefault_002dtheme_jsp._jspx_meth_c_005fchoose_005f0(pluto_002ddefault_002dtheme_jsp.java:321)
> at org.apache.jsp.WEB_002dINF.themes.pluto_002ddefault_002dtheme_jsp._jspService(pluto_002ddefault_002dtheme_jsp.java:160)
> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:331)
> at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:329)
> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
> at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:691)
> at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:469)
> at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:403)
> at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301)
> at org.apache.pluto.driver.PortalDriverServlet.doGet(PortalDriverServlet.java:196)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172)
> at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525)
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151)
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:874)
> at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
> at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
> at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
> at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689)
> at java.lang.Thread.run(Thread.java:619)
> ----
> But two questions arise:
> Why it tries to get the portlet application descriptor 3 times (one for each portlet view mode)? The first one failed, the rest should also fail.
> When this portlet must be initialized. I suppose that the first time we go to see the page... What class is reponsible of this?
> Because the portlet application descriptor is not in the context.
> Thank you very much!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.