ICEfaces
  1. ICEfaces
  2. ICE-7327

Timer already cancelled

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: EE-2.0.0.GA
          • Fix Version/s: 3.0.RC1, 3.0
          • Component/s: None
          • Labels:
            None
          • Environment:
            -
          • Assignee Priority:
            P1

            Description

            Customer is seeing "Timer already cancelled" when running 2.0 EE. It appears as though it occurs on the listen.icepush request, with or without page interaction by the user. This does not appear to be an issue with the AuctionMonitor sample.

            Attached is zip containing the following:

            1. Screenshots showing firebug network traces and errors
            2. localhost.2011-09-09.log showing stacktrace excptions
            3. logbandeau_erreur500.pcap : wireshark network traces
            4. localhost_access_log.2011-09-09.txt access log of tomcat

              Issue Links

              depends on

              Bug - A problem which impairs or prevents the functions of the product. PUSH-148 Servlet 3.0 ARP's timeout interferes with ICEpush' heartbeat mechanism

              • Major - Major loss of function.
              • Closed

                Activity

                Ascending order - Click to sort in descending order
                Hide
                Permalink
                Deryk Sinotte added a comment -

                Updating fix version and priority for supported customer. Please take a look at this as a priority please Mircea.

                Show
                Deryk Sinotte added a comment - Updating fix version and priority for supported customer. Please take a look at this as a priority please Mircea.
                Hide
                Permalink
                Mircea Toma added a comment -

                I tried to run 'auction' application with the clock turned on and off, both with icepush-ee and icefaces-ee features enabled and disabled. Still couldn't reproduce the issue.

                The environment used was Tomcat 7.0.20, async mode on, and JRE 1.6.0_26.

                Show
                Mircea Toma added a comment - I tried to run 'auction' application with the clock turned on and off, both with icepush-ee and icefaces-ee features enabled and disabled. Still couldn't reproduce the issue. The environment used was Tomcat 7.0.20, async mode on, and JRE 1.6.0_26.
                Hide
                Permalink
                Ted Goddard added a comment -

                The logs appear to contain two distinct Exceptions:

                Caused by: java.lang.IllegalStateException: The request associated with the AsyncContext has already completed processing.
                at org.apache.catalina.core.AsyncContextImpl.check(AsyncContextImpl.java:436)
                at org.apache.catalina.core.AsyncContextImpl.complete(AsyncContextImpl.java:87)
                at org.icepush.servlet.AsyncAdaptingServlet$AsyncRequestResponse.respondWith(AsyncAdaptingServlet.java:66)
                at org.icepush.BlockingConnectionServer.respondIfPendingRequest(BlockingConnectionServer.java:131)
                ... 38 more

                and

                java.lang.RuntimeException: java.lang.IllegalStateException: Timer already cancelled.
                at org.icefaces.impl.push.servlet.ICEpushResourceHandler$ICEpushResourceHandlerImpl.handleResourceRequest(ICEpushResourceHandler.java:226)
                at org.icefaces.impl.push.servlet.ICEpushResourceHandler.handleResourceRequest(ICEpushResourceHandler.java:110)
                at org.icefaces.impl.push.DynamicResourceDispatcher.handleResourceRequest(DynamicResourceDispatcher.java:81)
                at org.icefaces.application.ResourceRegistry.handleResourceRequest(ResourceRegistry.java:85)

                It seems possible that "Timer already cancelled" occurs during application shutdown and is not the cause of any functional problems. Please confirm if the tomcat instance was shut down before the logs were collected and if possible, confirm whether "AsyncContext has already completed processing" is the Exception related to the functional problems.

                Show
                Ted Goddard added a comment - The logs appear to contain two distinct Exceptions: Caused by: java.lang.IllegalStateException: The request associated with the AsyncContext has already completed processing. at org.apache.catalina.core.AsyncContextImpl.check(AsyncContextImpl.java:436) at org.apache.catalina.core.AsyncContextImpl.complete(AsyncContextImpl.java:87) at org.icepush.servlet.AsyncAdaptingServlet$AsyncRequestResponse.respondWith(AsyncAdaptingServlet.java:66) at org.icepush.BlockingConnectionServer.respondIfPendingRequest(BlockingConnectionServer.java:131) ... 38 more and java.lang.RuntimeException: java.lang.IllegalStateException: Timer already cancelled. at org.icefaces.impl.push.servlet.ICEpushResourceHandler$ICEpushResourceHandlerImpl.handleResourceRequest(ICEpushResourceHandler.java:226) at org.icefaces.impl.push.servlet.ICEpushResourceHandler.handleResourceRequest(ICEpushResourceHandler.java:110) at org.icefaces.impl.push.DynamicResourceDispatcher.handleResourceRequest(DynamicResourceDispatcher.java:81) at org.icefaces.application.ResourceRegistry.handleResourceRequest(ResourceRegistry.java:85) It seems possible that "Timer already cancelled" occurs during application shutdown and is not the cause of any functional problems. Please confirm if the tomcat instance was shut down before the logs were collected and if possible, confirm whether "AsyncContext has already completed processing" is the Exception related to the functional problems.
                Hide
                Permalink
                Ted Goddard added a comment -

                Choose "Notification", then choose "Simple Push" to reproduce in mobileshowcase-async.war.

                Show
                Ted Goddard added a comment - Choose "Notification", then choose "Simple Push" to reproduce in mobileshowcase-async.war.
                Hide
                Permalink
                Jack Van Ooststroom added a comment -

                The fix to PUSH-148: "Servlet 3.0 ARP's timeout interferes with ICEpush' heartbeat mechanism" resolved this issue. Marking this one as FIXED.

                Show
                Jack Van Ooststroom added a comment - The fix to PUSH-148 : "Servlet 3.0 ARP's timeout interferes with ICEpush' heartbeat mechanism" resolved this issue. Marking this one as FIXED.

                  People

                  • Assignee:
                    Jack Van Ooststroom
                    Reporter:
                    Tyler Johnson
                  • Votes:
                    0 Vote for this issue
                    Watchers:
                    0 Start watching this issue

                    Dates

                    • Created:
                      Updated:
                      Resolved: