ICEfaces
  1. ICEfaces
  2. ICE-5227

ICEfaces 2.0 Auction push failure

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 2.0-Alpha2
    • Fix Version/s: 2.0-Alpha3, 2.0.0
    • Component/s: Sample Apps
    • Labels:
      None
    • Environment:
      Server: Tomcat 6
      Browsers: IE6,7,8, FF3.5, Safari 4, Chrome 3, Opera 10 (Each has 2 tabs opened)

      Description

      When QA performing browser memory test on Tomcat 6 using multiple browsers described above, found in IE browsers (IE8,7,6), Safari 4 and Chrome 3, the clock stopped ticking after the test was started for about 10 minutes. A page reload would bring the clocks back to tick.

      This issue does not happen to FF3.5 and Opera 10.
      No exception/error showing in the server log files and server console.

        Issue Links

          Activity

          Hide
          Ted Goddard added a comment -

          Crash was observed again, re-opening issue.

          Show
          Ted Goddard added a comment - Crash was observed again, re-opening issue.
          Hide
          Ted Goddard added a comment -

          For the initial verification, cookies were cleared, and the test ran until the server was restarted.

          If cookies are not cleared and the test is restarted, it can be observed to crash within 10 minutes.

          There may be a problem with BROWSERID assignment: the ID before the ":" in the window name is different for the first window than the subsequent windows.

          Show
          Ted Goddard added a comment - For the initial verification, cookies were cleared, and the test ran until the server was restarted. If cookies are not cleared and the test is restarted, it can be observed to crash within 10 minutes. There may be a problem with BROWSERID assignment: the ID before the ":" in the window name is different for the first window than the subsequent windows.
          Hide
          Ted Goddard added a comment -

          Just before IE crashed it briefly displayed "The website 10.18.3.59 wants to save a file on your computer called a "cookie""

          Show
          Ted Goddard added a comment - Just before IE crashed it briefly displayed "The website 10.18.3.59 wants to save a file on your computer called a "cookie""
          Hide
          Ted Goddard added a comment -

          Some failures are due to Internet Explorer memory leaks. Request attribute resolves push failures under multiple browser connections, but push failures for long running connections need further investigation.

          Show
          Ted Goddard added a comment - Some failures are due to Internet Explorer memory leaks. Request attribute resolves push failures under multiple browser connections, but push failures for long running connections need further investigation.
          Hide
          Deryk Sinotte added a comment -

          Changes to remove the ThreadLocal and use request attributes have remedied the problem of staring push with multiple browsers instances running. However, push is still timing out after a variable amount of time which at this point does not look related to the type or version of browser.

          Our current data indicates that push groups are being cleaned up too early and the cause may be related to the calculation of the lastAccess time in PushContext.Group class. Typically, each incoming request with valid push ids would touch the lastAccess time indicating the push group was still valid. However, there seems to be an issue which causes these requests to not update the lastAccess time. Continuing to investigate.

          Show
          Deryk Sinotte added a comment - Changes to remove the ThreadLocal and use request attributes have remedied the problem of staring push with multiple browsers instances running. However, push is still timing out after a variable amount of time which at this point does not look related to the type or version of browser. Our current data indicates that push groups are being cleaned up too early and the cause may be related to the calculation of the lastAccess time in PushContext.Group class. Typically, each incoming request with valid push ids would touch the lastAccess time indicating the push group was still valid. However, there seems to be an issue which causes these requests to not update the lastAccess time. Continuing to investigate.

            People

            • Assignee:
              Mircea Toma
              Reporter:
              Joanne Bai
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: