IllegalStateException on Liferay 6.0 EE SP1

[Ankur Jaswal, modifié il y a 10 années.]

We are using Liferay 6.0 EE SP1, jsf-api-2.1.3-b02 and jsf-impl-2.1.3-b02, Liferay faces 3.0.1-ga2, Icefaces 3.2.0 jars we are getting seeing this exception below. Are we using the combination of the jars supported by Liferay faces. Ones this exception happens we cant access the portal

18:43:16,645 ERROR [jsp:154] java.lang.IllegalStateException: Could not find backup for factory javax.faces.lifecycle.LifecycleFactory.
at javax.faces.FactoryFinder$FactoryManager.getFactory(FactoryFinder.java:1008)
at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:343)
at com.liferay.faces.bridge.BridgePhaseBaseImpl.<init>(BridgePhaseBaseImpl.java:103)
at com.liferay.faces.bridge.BridgePhaseCompatImpl.<init>(BridgePhaseCompatImpl.java:38)
at com.liferay.faces.bridge.BridgePhaseRenderImpl.<init>(BridgePhaseRenderImpl.java:66)
at com.liferay.faces.bridge.BridgePhaseFactoryImpl.getBridgeRenderPhase(BridgePhaseFactoryImpl.java:49)
at com.liferay.faces.bridge.BridgeImpl.doFacesRequest(BridgeImpl.java:110)
at javax.portlet.faces.GenericFacesPortlet.doView(GenericFacesPortlet.java:255)
at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:328)
at javax.portlet.faces.GenericFacesPortlet.doDispatch(GenericFacesPortlet.java:204)
at javax.portlet.GenericPortlet.render(GenericPortlet.java:233)
at com.liferay.portlet.FilterChainImpl.doFilter(FilterChainImpl.java:101)
at com.liferay.portal.kernel.portlet.PortletFilterUtil.doFilter(PortletFilterUtil.java:64)
at com.liferay.portlet.InvokerPortletImpl.invoke(InvokerPortletImpl.java:653)
at com.liferay.portlet.InvokerPortletImpl.invokeRender(InvokerPortletImpl.java:724)
at com.liferay.portlet.InvokerPortletImpl.render(InvokerPortletImpl.java:426)
at org.apache.jsp.html.portal.render_005fportlet_jsp._jspService(render_005fportlet_jsp.java:1387)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:377)

[Neil Griffin, modifié il y a 10 années.]

Do you have an <instanceable> section in your portlet's WEB-INF/liferay-portlet.xml? If so what is the value?

[Ankur Jaswal, modifié il y a 10 années.]

its is true

<portlet>
<portlet-name>TransactionHistory</portlet-name>
<instanceable>true</instanceable>
<header-portlet-css>/resources/css/main.css</header-portlet-css>
<header-portlet-css>/resources/css/custom.css</header-portlet-css>
<footer-portlet-javascript>/resources/js/main.js</footer-portlet-javascript>
</portlet>

[Neil Griffin, modifié il y a 10 années.]

Do you programmatically add the portlet to the portal page, or did you do it manually by clicking "Add Application" with the portal's web-based user interface?

[Ankur Jaswal, modifié il y a 10 années.]

We manually drag the portlet to the page using Liferay UI interface.

[Neil Griffin, modifié il y a 10 années.]

Do you have other JSF portlets on the page besides this one?

[Ankur Jaswal, modifié il y a 10 années.]

In one page we have one portlet.

We do have other portlets in all 27 portlets. We are using icefaces 3.2.0 jars and using iceface in compatibility mode. so there are some ice tags like ice:output or ice:panelGrid or ice:form in some of the portlets and some we converted to h:form and using ace:dataTable tag


We used the following dependency in the pom to get the faces jars

<dependency>
<groupId>com.liferay.faces</groupId>
<artifactId>liferay-faces-alloy</artifactId>
<version>3.0.1-ga2</version>
</dependency>
<dependency>
<groupId>com.liferay.faces</groupId>
<artifactId>liferay-faces-bridge-impl</artifactId>
<version>3.0.1-ga2</version>
</dependency>
<dependency>
<groupId>com.liferay.faces</groupId>
<artifactId>liferay-faces-portal</artifactId>
<version>3.0.1-ga2</version>
</dependency>

The liferay-portlet.xml has the following at the top
<?xml version="1.0"?>
<!DOCTYPE liferay-portlet-app PUBLIC "-//Liferay//DTD Portlet Application 6.0.0//EN" "http://www.liferay.com/dtd/liferay-portlet-app_6_0_0.dtd">

Not sure if that matters

[Neil Griffin, modifié il y a 10 années.]

Does the problem only happen with the TransactionHistory portlet? In other words, if you were to delete webapps/TransactionHistory would the problem go away?

[Ankur Jaswal, modifié il y a 10 années.]

Sorry I was wrong - there was another page that had two portlets on it - one was old one not converted to jsf-2 (was showing not available) and new one jsf-2. And when I access the new one was getting the java.lang.IllegalStateException. Now I deleted the old one and we do not get the exception. Thanks for your help

[Neil Griffin, modifié il y a 10 années.]

Glad to hear that it is working. We ran into a similar error during testing recently. For more info, see FACES-1584.