Zac Moskovitch
Zac Moskovitch
I tried to reproduce this issue but didn't manage to do so, In my case it failed with the exception `okhttp3.internal.http2.StreamResetException: stream was reset: CANCEL` I didn't manage to get...
@rzo1 It’s really good that you found the exception about “disconnected for operational reasons”, this can be a clue for investigating it on the server side. The provided solution related...
Thanks for the update @rzo1 , I think that the fix you described relates to how to handle [server maintenance](https://developer.twitter.com/en/docs/tutorials/stream-tweets-in-real-time#:~:text=Server%20maintenance%3A%20The%20Twitter%20team%20deployed%20a%20change%20or%20update%20to%20the%20system%20servers) @yssoe , did you manage to find if you also...
Please check [this link](https://developer.twitter.com/en/docs/twitter-api/tweets/filtered-stream/integrate/handling-disconnections) A reconnect is expected when server is restarted. Most common errors are `OperationalDisconnectProblem` or `ConnectionExceptionProblem` @yssoe , can you please try it after modifying your code?...
@rzo1 , thank you for the update. Can you please share your code? Just to follow the code in case of the operational exception. Regarding waiting before a reconnect, please...
As far as I checked, you should back off when reconnecting for best practice. I'll continue checking it. In addition to this I've updated the new [branch](https://github.com/twitterdev/twitter-api-java-sdk/tree/stream-timeout)
Hi @rzo1, I tried it several times, as far as I checked it looks that waiting before the reconnect enables to stream the tweets properly.
Thank you for the PR, As mentioned in the issue, the fix will be done in the API response and not as part of the SDK. Regarding the files names,...
Hi @kisaga , thank you for your PR. I really appreciate your effort and willingness to improve the Twitter APIs Java SDK. After checking your PR these are my comments:...
@nrv, thank you for opening this issue, the fix will be done at the API level and not inside the SDK. We'll let you know once it's done.