ICEfaces
  1. ICEfaces
  2. ICE-1339

Async communication mode doesn't work across multiple apps using same host-name

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.6DR#1
    • Fix Version/s: 1.7
    • Component/s: Bridge
    • Labels:
      None
    • Environment:
      Any
    • Affects:
      Documentation (User Guide, Ref. Guide, etc.)
    • Workaround Exists:
      Yes
    • Workaround Description:
      Hide
      Workaround is to configure a proxy server to always provide each application with it's own host-name, thus avoiding the 2-connection per host HTTP 1.1 limit.

      Alternative workaround is to configure and use the Async Server (EPS).
      Show
      Workaround is to configure a proxy server to always provide each application with it's own host-name, thus avoiding the 2-connection per host HTTP 1.1 limit. Alternative workaround is to configure and use the Async Server (EPS).

      Description

      The enhancement made in ICE-825 to support concurrentDOMviews is working nicely when viewing the same application in multiple browser windows/tabs concurrently.

      However, communications freeze for all applications in the situation where you have more than one async ICEfaces application running on the same host with each being viewed in a separate browser window/tab (but not a separate browser application instance).

      This may be related to the URL path that the cookie passing scheme uses to share a single async connection between browser windows, as each application on the same host will have a different URL.

        Activity

        Ken Fyten created issue -
        Ken Fyten made changes -
        Field Original Value New Value
        Assignee Mircea Toma [ mircea.toma ]
        Ken Fyten made changes -
        Fix Version/s 1.6 [ 10031 ]
        Affects [Documentation (User Guide, Ref. Guide, etc.)]
        Assignee Priority P2
        Ken Fyten made changes -
        Workaround Description Workaround is to configure a proxy server to always provide each application with it's own host-name, thus avoiding the 2-connection per host HTTP 1.1 limit. Workaround is to configure a proxy server to always provide each application with it's own host-name, thus avoiding the 2-connection per host HTTP 1.1 limit.

        Alternative workaround is to configure and use the Async Server (EPS).
        Fix Version/s 1.6 [ 10031 ]
        Ken Fyten made changes -
        Assignee Mircea Toma [ mircea.toma ]
        Ken Fyten made changes -
        Status Open [ 1 ] Closed [ 6 ]
        Fix Version/s 1.7 [ 10080 ]
        Assignee Priority P2
        Resolution Fixed [ 1 ]

          People

          • Assignee:
            Unassigned
            Reporter:
            Ken Fyten
          • Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: