Details
-
Type:
Bug
-
Status: Closed
-
Priority:
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
-
Assignee Priority:P1
-
Support Case References:Support Case #13319 - https://icesoft.my.salesforce.com/50070000013VNaA
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.
[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
- depends on
-
PUSH-349 Callback mechanism for error-free blocking connection running
-
- Closed
-
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.