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

              Repository Revision Date User Message
              ICEsoft Public SVN Repository #21512 Thu May 27 14:18:04 MDT 2010 mircea.toma PUSH-87 Fix typo.
              Files Changed
              Commit graph MODIFY /scratchpads/snowplow/core/src/main/javascript/command.js
              Repository Revision Date User Message
              ICEsoft Public SVN Repository #21504 Thu May 27 10:14:46 MDT 2010 mircea.toma PUSH-87 Avoid sending X-Connection=close header durign the bridge during fail-over.
              Files Changed
              Commit graph MODIFY /scratchpads/snowplow/core/src/main/java/org/icepush/servlet/BrowserBoundServlet.java
              Repository Revision Date User Message
              ICEsoft Public SVN Repository #21503 Thu May 27 10:11:31 MDT 2010 mircea.toma PUSH-87 Avoid sending X-Connection=close header durign the bridge during fail-over.
              Files Changed
              Commit graph MODIFY /scratchpads/snowplow/core/src/main/java/org/icepush/BlockingConnectionServer.java

                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: