[jboss-user] [JBoss Portal Users] - RichFaces Portlet causes timeout Exception
Hello,
I have implemented a RichFaces portlet which has just one page view from which the actions
do not cause the portlet to navigate away. The Portlet has quite a few RichFaces
components including rich:tree ... for the most part these components interact and work
fine.
But the portlet after about 10 minutes of inactivity throws the following Exception and
crashes here is the stack trace ...
javax.faces.FacesException: No saved portlet window state for an id
736b023d-3b0d-480d-9c23-6027130534ab:view:8c4c06b4-d05d-41b1-9689-3a6e1b763829
at
org.jboss.portletbridge.context.ServletExternalContextImpl.(ServletExternalContextImpl.java:101)
at
org.jboss.portletbridge.context.FacesContextFactoryImpl.getFacesContext(FacesContextFactoryImpl.java:164)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:260)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178)
at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290)
at
org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:368)
at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:495)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at
org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182)
at
org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at
org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
at java.lang.Thread.run(Thread.java:619)
I have set the following parameter as well but it seems to have no impact:
<session-config>
<session-timeout>120</session-timeout>
</session-config>
Any pointers to why this is perhaps occurring would be deeply appreciated ...
Regards,
-- Brian
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4261302#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...