Affects Version/s: None
Fix Version/s: 4.1, EE-3.3.0.GA_P04
Affects:Documentation (User Guide, Ref. Guide, etc.)
Although ICEpush supports automatic retries for failed heartbeat connections, we don’t do the same for failed push update retrieval attempts. Instead, we treat these the same as user-initiated requests that will immediately fail due to a network error.
It would be friendlier if IcePush would handle failed push update retrievals by automatically retrying in a manner similar to that used for the existing heartbeat connections.
The existing org.icepush.networkErrorRetryTimeouts configuration could be used for both heartbeat connection failures and push update retrieval failures.
This change is especially important for push update retrieval requests which happen behind the scenes unbeknownst to the user. If I was a user, I might be confused by an asynchronous NCI popup that blocks further operations on my window due to a failed background ajax update which, if retried, would likely succeed.
- Remote Attachments
Implemented automatic retry capability for failed push update retrieval. Also introduced org.icefaces.updateNetworkErrorRetryTimeouts context parameter to configure the intervals at which the bridge will retry to acquire the updates. The parameter value should be a list of space separated numbers which represent the retry intervals in milliseconds. The default value is '1000 2000 3000'.