-
Notifications
You must be signed in to change notification settings - Fork 168
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
Unhandled {error,closed} in state connected causes crash #239
Comments
to understand your trouble, could you give me code example? |
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After having established a connection and it's having been closed an attempt is made to re-establish that connection presumably if that attempt unexpectedly fails the following occurs:
From a monitor {'EXIT',<0.29920.2>,{error,closed}}
19:35:49.593 [error] gen_statem <0.29920.2> in state connected terminated with reason: {{error,closed},state_functions}
19:35:49.594 [error] CRASH REPORT Process <0.29920.2> with 0 neighbours exited with reason: {error,closed} in gen_statem:loop_state_callback_result/11 line 1548
rebar.lock
The text was updated successfully, but these errors were encountered: