-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connection state is not changed to Open from Connecting #21
Comments
interesting do you have a reproduction case? |
Unfortunately, no. I have no idea why it's happening. It's completely
random and happens one-two times per week.
…On Mon, Jul 15, 2019, 22:31 Allen Byron Penner ***@***.***> wrote:
interesting do you have a reproduction case?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#21?email_source=notifications&email_token=ACTEAILXOJ2NKSM54J7FC6LP7SQ63A5CNFSM4IDS64TKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZ6HVQY#issuecomment-511474371>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACTEAINMSMLU5MEYAOZ5HRLP7SQ63ANCNFSM4IDS64TA>
.
|
Some additional info. I am trying to reproduce this error, Looks like it impossible, because I cannot create the state when it happens. But I have some additional logs:
When everything goes fine then I see the following in the log:
As you can see there is But, below you can see the case when the lib could reconnect but the state didn't change:
So, we can see |
good work thank that gives me some good places to look |
Hello. I see a lot of exceptions in my log files and they are pretty the same:
Why does it happen?
But, it's not a big problem. Recconection strategy usually handles it. BUT, not always, the library is stuck in
Connecting
state:As you can see in the logs above, there was error and the library reconnected
Aborted => Connecting => Open
, but sometimes the library just change state toConnecting
and that's it. There is no any messages/errors after that.PS. I use standard reconection strategy:
new ReconnectStrategy(2000, 4000)
The text was updated successfully, but these errors were encountered: