ICEfaces
  1. ICEfaces
  2. ICE-4312

Push Server does not unblock a previous blocking request when a new app is opened

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.8RC2
    • Fix Version/s: 1.8
    • Component/s: Framework
    • Labels:
      None
    • Environment:
      ICEfaces Core, Push Server

      Description

      The Push Server is not unblocking a pending blocking request when a new blocking request is received due to opening a new asynchronous ICEfaces application in a new tab within the same browser instance.

        Activity

        Hide
        Jack Van Ooststroom added a comment -

        Changed Fix Version(s) to 1.8.0

        Show
        Jack Van Ooststroom added a comment - Changed Fix Version(s) to 1.8.0
        Hide
        Jack Van Ooststroom added a comment -

        The Push Server's logic was incorrect. Basically, the following happened:

        1. There's an outstanding blocking receive-updated-views request to the Push Server for ICEfaces application 1 with ICEfaces ID 1.
        2. A new tab is opened to ICEfaces application 2 with ICEfaces ID 2.
        3. A new blocking receive-updated-views request to the Push Server is issued but now with ICEfaces IDs 1 and 2.
        4. Due to incorrect logic the previous blocking receive-updated-views request with ICEfaces ID 1 is not unblocked.

        When 3. occurs, any outstanding blocking receive-updated-views request with an ICEfaces ID contained in the new blocking receive-updated-views request should be unblocked.

        The improved logic is in place. Marking this one as FIXED.

        Show
        Jack Van Ooststroom added a comment - The Push Server's logic was incorrect. Basically, the following happened: 1. There's an outstanding blocking receive-updated-views request to the Push Server for ICEfaces application 1 with ICEfaces ID 1. 2. A new tab is opened to ICEfaces application 2 with ICEfaces ID 2. 3. A new blocking receive-updated-views request to the Push Server is issued but now with ICEfaces IDs 1 and 2. 4. Due to incorrect logic the previous blocking receive-updated-views request with ICEfaces ID 1 is not unblocked. When 3. occurs, any outstanding blocking receive-updated-views request with an ICEfaces ID contained in the new blocking receive-updated-views request should be unblocked. The improved logic is in place. Marking this one as FIXED.

          People

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

            Dates

            • Created:
              Updated:
              Resolved: