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

          Joanne Bai created issue -
          Joanne Bai made changes -
          Field Original Value New Value
          Assignee Ken Fyten [ ken.fyten ]
          Ken Fyten made changes -
          Salesforce Case []
          Assignee Priority P2
          Assignee Ken Fyten [ ken.fyten ] Ted Goddard [ ted.goddard ]
          Ken Fyten made changes -
          Salesforce Case []
          Fix Version/s 2.0-Alpha2 [ 10214 ]
          Ken Fyten made changes -
          Salesforce Case []
          Assignee Priority P2 P1
          Assignee Ted Goddard [ ted.goddard ] Mircea Toma [ mircea.toma ]
          Priority Major [ 3 ] Critical [ 2 ]
          Mircea Toma made changes -
          Status Open [ 1 ] Resolved [ 5 ]
          Resolution Fixed [ 1 ]
          Ken Fyten made changes -
          Resolution Fixed [ 1 ]
          Status Resolved [ 5 ] Reopened [ 4 ]
          Ken Fyten made changes -
          Comment [ Still failing on IE browsers:

          Clocks tick for me on Firefox (perhaps this is what was
          fixed by clearing the cookies).

          However, with IE 6, I have verified that the notifications
          are being received and retrieveUpdate() is being called
          in the browser, but an exception is being thrown in this
          method:

          "failed to pick updates[object error]"

          (Looks like the exception doesn't have a proper toString()).

          Ted. ]
          Ken Fyten made changes -
          Comment [ Using e.name and e.message, the exception appears to be:

          updateException Invalid argument

          So perhaps we are passing something strange to jsf.ajax.request.
          ]
          Ken Fyten made changes -
          Status Reopened [ 4 ] Resolved [ 5 ]
          Assignee Priority P1
          Resolution Fixed [ 1 ]
          Ted Goddard made changes -
          Resolution Fixed [ 1 ]
          Status Resolved [ 5 ] Reopened [ 4 ]
          Ken Fyten made changes -
          Salesforce Case []
          Assignee Priority P1
          Ken Fyten made changes -
          Link This issue depends on PUSH-23 [ PUSH-23 ]
          Ken Fyten made changes -
          Salesforce Case []
          Fix Version/s 2.0-Beta [ 10032 ]
          Fix Version/s 2.0-Alpha2 [ 10214 ]
          Assignee Priority P1 P2
          Ken Fyten made changes -
          Status Reopened [ 4 ] Resolved [ 5 ]
          Assignee Priority P2
          Resolution Fixed [ 1 ]
          Ken Fyten made changes -
          Fix Version/s 2.0.0 [ 10230 ]
          Ken Fyten made changes -
          Status Resolved [ 5 ] Closed [ 6 ]

            People

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

              Dates

              • Created:
                Updated:
                Resolved: