Details
-
Bug
-
Status: Closed
-
Resolution: No Longer Reproducible
-
7.0.0 DXP SP4, 7.0.X
-
4
-
Ubuntu LTS 16.04
-
Oracle OpenJDK 8
-
Apache Tomcat 8.0.x
-
PostgreSQL 9.4
Description
After tomcat restart portlet is not working and dont have some of imported packages in gogo shell.
Steps
- Start Portal
- Deploy WAR from attachment - sample-spring-mvc-freemarker-portlet-1.0-SNAPSHOT.war
- Add portlet -> Add -> Applications -> Sample -> Spring MVC Freemarker portlet
- Restart Tomcat
- Open page with portlet
Expected
Portlet is working correctly after tomcat restart
Actual
Portlet have missing some of imported package in GoGo shell and is not working correctly and throws:
17:51:18,473 ERROR [http-nio-8080-exec-1][render_portlet_jsp:131] null
lf7-dxp-as | org.springframework.web.portlet.NoHandlerFoundException: No handler found for portlet request: mode 'view', phase 'RENDER_PHASE', parameters map[[empty]]
lf7-dxp-as | at javax.portlet.GenericPortlet.render(GenericPortlet.java:259)
Note
Missing imported package are:
com.liferay.portal.osgi.web.servlet.jsp.compiler; version="2.0.0" <com.liferay.portal.osgi.web.servlet.jsp.compiler_2.0.24 [12]>
com.liferay.taglib.aui; version="7.3.0" <com.liferay.util.taglib_2.9.0 [552]>
com.liferay.taglib.portlet; version="7.1.0" <com.liferay.util.taglib_2.9.0 [552]>
com.liferay.taglib.portletext; version="7.2.0" <com.liferay.util.taglib_2.9.0 [552]>
com.liferay.taglib.security; version="7.0.0" <com.liferay.util.taglib_2.9.0 [552]>
com.liferay.taglib.theme; version="7.2.0" <com.liferay.util.taglib_2.9.0 [552]>
com.liferay.taglib.ui; version="7.7.0" <com.liferay.util.taglib_2.9.0 [552]>
com.liferay.taglib.util; version="7.3.0" <com.liferay.util.taglib_2.9.0 [552]>
org.eclipse.core.runtime; version="2.0.0" <com.liferay.portal.osgi.web.wab.extender_2.0.18 [13]>
Possible workarounds:
1.) Uninstall portlet via gogo shell before tomcat restart
2.) Add some .jsp file and spring-context.xml to WEB-INF - attachment sample-spring-mvc-freemarker-portlet-1.0-SNAPSHOT-with-jsp-and-spring-xml.war
3.) Rebuild portlet and redeploy (after restart its now working again)