You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The code seems to expect a heartbeat response every 45s but I'm not seeing any, at least while connected to Office365. This causes the underlying http connection to time out before lifetime minutes is reached, unless I've made sure that ExchangeService has a much larger timeout than would be applicable to other requests.
A simple fix would be to set the http request timeout to lifetime minutes just for the hanging GetStreamingEvents call.
The text was updated successfully, but these errors were encountered:
dconnelly
added a commit
to slack-migrations/ews-java-api
that referenced
this issue
Feb 15, 2016
…equest basis.
This allows the GetStreamingEvents call to specify a longer timeout so connection is not
dropped before lifetime minutes has been reached. Relying on heartbeats to keep the
connection alive does not seem to work for Office365.
dconnelly
added a commit
to slack-migrations/ews-java-api
that referenced
this issue
Feb 15, 2016
…equest basis.
This allows the GetStreamingEvents call to specify a longer timeout so connection is not
dropped before lifetime minutes has been reached. Relying on heartbeats to keep the
connection alive does not seem to work for Office365.
The code seems to expect a heartbeat response every 45s but I'm not seeing any, at least while connected to Office365. This causes the underlying http connection to time out before lifetime minutes is reached, unless I've made sure that ExchangeService has a much larger timeout than would be applicable to other requests.
A simple fix would be to set the http request timeout to lifetime minutes just for the hanging GetStreamingEvents call.
The text was updated successfully, but these errors were encountered: