ICEpush
  1. ICEpush
  2. PUSH-87

Fail-over is not possible when a node is taken down normally

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.0-Alpha2
    • Fix Version/s: 2.0.0
    • Component/s: Push Library
    • Labels:
      None
    • Environment:
      ICEpush, Cluster

      Description

      Currently fail-over is not possible when a node in the cluster is taken down gracefully. In this case the Core sends an X-Connection: close response to the blocking request, causing the JavaScript Bridge evidently not to try and re-establish the blocking connection. Maybe we can make a distinction somehow between shutting down a standalone server and shutting down one or more nodes within a cluster.

        Activity

        Hide
        Jack Van Ooststroom added a comment -

        Assigning to Mircea for investigation.

        Show
        Jack Van Ooststroom added a comment - Assigning to Mircea for investigation.
        Hide
        Mircea Toma added a comment -

        When contextPath is defined we can assume that EPS & clustering is used. Only then the server will stop sending X-Connection=close header during shutdown/fail-over.

        Show
        Mircea Toma added a comment - When contextPath is defined we can assume that EPS & clustering is used. Only then the server will stop sending X-Connection=close header during shutdown/fail-over.
        Hide
        Jack Van Ooststroom added a comment -

        Fail-over works fine when doing a graceful shutdown for both ICEpush and ICEfaces. Marking this one as FIXED again.

        Show
        Jack Van Ooststroom added a comment - Fail-over works fine when doing a graceful shutdown for both ICEpush and ICEfaces. Marking this one as FIXED again.

          People

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

            Dates

            • Created:
              Updated:
              Resolved: