ICEpush
  1. ICEpush
  2. PUSH-82

JavaScript Bridge does not try to reconnect after blocking connection is severed

          Details

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

            Description

            The JavaScript Bridge does not try to establish the blocking connection again, after it has been severed.

              Activity

              Ascending order - Click to sort in descending order
              Jack Van Ooststroom created issue -
              Hide
              Permalink
              Jack Van Ooststroom added a comment -

              Assigning to Mircea for investigation.

              Show
              Jack Van Ooststroom added a comment - Assigning to Mircea for investigation.
              Jack Van Ooststroom made changes -
              Field Original Value New Value
              Assignee Mircea Toma [ mircea.toma ]
              Repository Revision Date User Message
              ICEsoft Public SVN Repository #21298 Fri Apr 23 08:36:19 MDT 2010 mircea.toma PUSH-82 Introduce timeout mechanism for detecting inactive blocking connection and retry re-establish connection.
              Files Changed
              Commit graph MODIFY /scratchpads/snowplow/core/src/main/javascript/connection.async.js
              Commit graph MODIFY /scratchpads/snowplow/core/src/main/java/org/icepush/ConfigurationServer.java
              Hide
              Permalink
              Mircea Toma added a comment -

              Introduced connection inactivity mechanism. The mechanism assumes that the blocking connection is regularly unblocked by the server-side heartbeat. When no response (connection unblocked) is received after a period of time (equal to the heartbeat period) the blocking connection is re-initiated. A second try is initiated if necessary after which the blocking connection is considered to be down (server not responding or no network access).

              Show
              Mircea Toma added a comment - Introduced connection inactivity mechanism. The mechanism assumes that the blocking connection is regularly unblocked by the server-side heartbeat. When no response (connection unblocked) is received after a period of time (equal to the heartbeat period) the blocking connection is re-initiated. A second try is initiated if necessary after which the blocking connection is considered to be down (server not responding or no network access).
              Mircea Toma made changes -
              Status Open [ 1 ] Resolved [ 5 ]
              Resolution Fixed [ 1 ]
              Hide
              Permalink
              Mircea Toma added a comment -

              Here's why severed connections cannot be detected on the client: http://windyroad.org/2006/08/16/ajax-error-handling/

              Show
              Mircea Toma added a comment - Here's why severed connections cannot be detected on the client: http://windyroad.org/2006/08/16/ajax-error-handling/
              Repository Revision Date User Message
              ICEsoft Public SVN Repository #21306 Mon Apr 26 05:47:07 MDT 2010 mircea.toma PUSH-82 Invoke 'connection trouble' listeners when blocking connection is not excercised as expected.
              Files Changed
              Commit graph MODIFY /scratchpads/snowplow/core/src/main/javascript/connection.async.js
              Ken Fyten made changes -
              Fix Version/s 2.0.0 [ 10233 ]
              Ken Fyten made changes -
              Status Resolved [ 5 ] Closed [ 6 ]

                People

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

                  Dates

                  • Created:
                    Updated:
                    Resolved: