ICEpush
  1. ICEpush
  2. PUSH-370

Make configurable network error retries

          Details

          • Type: Improvement Improvement
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 4.0, EE-3.3.0.GA_P03
          • Fix Version/s: 4.1, EE-3.3.0.GA_P04
          • Component/s: JavaScript Client
          • Labels:
            None
          • Environment:
            supported browsers
          • Assignee Priority:
            P1

            Description

            We need to make the number of retries when network failures are detected configurable. This way the application can be tailored to the network it is running in.

              Activity

              Ascending order - Click to sort in descending order
              Hide
              Permalink
              Ken Fyten added a comment -

              How about this?

              org.icepush.networkErrorRetryTimeouts - A space separated list of timeout intervals measured in milliseconds. When a network error is detected the bridge will use the first interval in the list to delay the push connection retry, if it receives a network error again it will use the second value and so on. Once the end of the list is reached the bridge will give up trying to establish the connection, and an Network Connection Interrupted (NCI) message will be displayed (unless disabled). The default value is 30000 30000 60000 60000.
              Show
              Ken Fyten added a comment - How about this? org.icepush.networkErrorRetryTimeouts - A space separated list of timeout intervals measured in milliseconds. When a network error is detected the bridge will use the first interval in the list to delay the push connection retry, if it receives a network error again it will use the second value and so on. Once the end of the list is reached the bridge will give up trying to establish the connection, and an Network Connection Interrupted (NCI) message will be displayed (unless disabled). The default value is 30000 30000 60000 60000.
              Hide
              Permalink
              Mircea Toma added a comment - - edited

              Introduced org.icepush.networkErrorRetryTimeouts context parameter to configure the number of retries attempted by ICEpush to re-connect with the server. Instead of using intervals in milliseconds the parameter will take a space separated list of multiplication factors (greater or equal to 1) for the heartbeat interval. This way the calculated intervals between retries will still work when the heartbeat is changed dynamically. The default value is '1 1 1 2 2 3'. For a fixed heartbeat timeout of 5000ms the intervals would translate to 5000ms, 5000ms, 5000ms, 10000ms, 10000ms and 15000ms.

              Show
              Mircea Toma added a comment - - edited Introduced org.icepush.networkErrorRetryTimeouts context parameter to configure the number of retries attempted by ICEpush to re-connect with the server. Instead of using intervals in milliseconds the parameter will take a space separated list of multiplication factors (greater or equal to 1) for the heartbeat interval. This way the calculated intervals between retries will still work when the heartbeat is changed dynamically. The default value is '1 1 1 2 2 3'. For a fixed heartbeat timeout of 5000ms the intervals would translate to 5000ms, 5000ms, 5000ms, 10000ms, 10000ms and 15000ms .
              Hide
              Permalink
              Mircea Toma added a comment -

              Added Wiki documentation for the new context parameter: http://www.icesoft.org/wiki/display/PUSH/ICEpush+Configuration+Parameters .

              Show
              Mircea Toma added a comment - Added Wiki documentation for the new context parameter: http://www.icesoft.org/wiki/display/PUSH/ICEpush+Configuration+Parameters .

                People

                • Assignee:
                  Mircea Toma
                  Reporter:
                  Mircea Toma
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: