ICEfaces
  1. ICEfaces
  2. ICE-10519

ice:outputConnectionStatus - Caution state not being changed

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: EE-3.3.0.GA_P02
    • Fix Version/s: EE-3.3.0.GA_P03
    • Component/s: ICE-Components
    • Labels:
      None
    • Environment:
      All

      Description

      A customer has reported that sometimes the ice:outputConnectionStatus component will report that the connection is in trouble via the yellow warning state, when receiving an ICEpush update. The browser console logs show that this is the case:

      [icepush.7c172.async-connection] [Tue, 24 Feb 2015 21:13:26 UTC] failed to connect, first retry...
      [icepush.7c172] [Tue, 24 Feb 2015 21:13:26 UTC] connection in trouble

      The connection is not lost and does continue to function but the yellow state is still applied. A browser refresh or another action is required to revert this.

        Issue Links

          Activity

          Arran Mccullough created issue -
          Arran Mccullough made changes -
          Field Original Value New Value
          Assignee Ken Fyten [ ken.fyten ]
          Ken Fyten made changes -
          Assignee Ken Fyten [ ken.fyten ] Mircea Toma [ mircea.toma ]
          Fix Version/s EE-3.3.0.GA_P03 [ 11572 ]
          Priority Major [ 3 ] Minor [ 4 ]
          Assignee Priority P1 [ 10010 ]
          Mircea Toma made changes -
          Link This issue depends on PUSH-349 [ PUSH-349 ]
          Hide
          Mircea Toma added a comment - - edited

          Modified status.js to turn off 'connection in trouble' indicator whenever a normal server response is received. The change uses the new ice.blockingConnectionReceive callback introduced by PUSH-349 for resetting the connection indicator.

          Show
          Mircea Toma added a comment - - edited Modified status.js to turn off 'connection in trouble' indicator whenever a normal server response is received. The change uses the new ice.blockingConnectionReceive callback introduced by PUSH-349 for resetting the connection indicator.
          Mircea Toma made changes -
          Status Open [ 1 ] Resolved [ 5 ]
          Resolution Fixed [ 1 ]
          Hide
          Mircea Toma added a comment -

          No, the async connection cannot be active when the server cannot be reached. The connection status will not go right away into 'caution' state, it will take 30 seconds (or whatever the value of heartbeat timeout is) for the bridge to detect that the server is not responding.

          Show
          Mircea Toma added a comment - No, the async connection cannot be active when the server cannot be reached. The connection status will not go right away into 'caution' state, it will take 30 seconds (or whatever the value of heartbeat timeout is) for the bridge to detect that the server is not responding.
          Ken Fyten made changes -
          Status Resolved [ 5 ] Closed [ 6 ]

            People

            • Assignee:
              Mircea Toma
              Reporter:
              Arran Mccullough
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: