Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.0-Alpha2
-
Fix Version/s: 2.0-Alpha3, 2.0.0
-
Component/s: Framework
-
Labels:None
-
Environment:jsf2.0, ICEfaces2, compat jars, JBoss 6.0 M2
Description
13:42:52,782 ERROR [STDERR] Exception in thread "pool-5-thread-1" java.lang.RuntimeException: FacesContext is not present for thread Thread[pool-5-thread-1,5,jboss]
13:42:52,810 ERROR [STDERR] at org.icefaces.application.PushRenderer.missingFacesContext(PushRenderer.java:122)
13:42:52,810 ERROR [STDERR] at org.icefaces.application.PushRenderer.render(PushRenderer.java:104)
13:42:52,810 ERROR [STDERR] at org.icefaces.application.showcase.view.bean.examples.component.progressBar.OutputProgressController$LongOperationRunner.run(OutputProgressController.java:132)
13:42:52,811 ERROR [STDERR] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
13:42:52,811 ERROR [STDERR] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
13:42:52,811 ERROR [STDERR] at java.lang.Thread.run(Thread.java:637)
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Appears resolved by ICE-5609.
Glimmer revision 21361
Server: Jboss-6.0.0.M2
Different exception is seen when loading Progress bar:
2010-05-05 13:59:03,268 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/component-showcase].[Faces Servlet]] (http-127.0.0.1-8080-6) Servlet.service() for servlet Faces Servlet threw exception: java.lang.RuntimeException: Query does not contain parameter named: ice.view
at org.icefaces.push.servlet.ServletRequestResponse.checkExistenceOf(ServletRequestResponse.java:304)
at org.icefaces.push.servlet.ServletRequestResponse.getParameterAsStrings(ServletRequestResponse.java:141)
at org.icefaces.push.DisposeWindowScope.service(DisposeWindowScope.java:23)
at org.icefaces.push.servlet.BasicAdaptingServlet.service(BasicAdaptingServlet.java:38)
at org.icefaces.push.servlet.PathDispatcher.service(PathDispatcher.java:45)
at org.icefaces.push.servlet.SessionDispatcher.service(SessionDispatcher.java:77)
at org.icefaces.push.servlet.ICEfacesResourceHandler.service(ICEfacesResourceHandler.java:141)
at org.icefaces.push.servlet.ICEfacesResourceHandler.handleResourceRequest(ICEfacesResourceHandler.java:102)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:310)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:336)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:276)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:183)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:95)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
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:158)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:872)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951)
at java.lang.Thread.run(Thread.java:619)
Progress bar works in FF3.5, but not in IE8 after loaded. Should this jira be reopened?
Since this is the "compat" component showcase, this use of PushRenderer should make use of SessionRenderer.
An alternative fix will be to use PortableRenderer (but this should be considered only if the above fails).