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
handle_disconnect works perfectly for infinite reconnection like in issue 5 - when host got down after some time
but it does not handle connection error in WebSockex.start_link - so if there is no connection to host, application does not start: 21:18:29.799 [info] Application arbi exited: Arbi.Application.start(:normal, []) returned an error: shutdown: failed to start child: Arbi.WsSup ** (EXIT) shutdown: failed to start child: Arbi.WsWorker ** (EXIT) %WebSockex.ConnError{original: :econnrefused}
The text was updated successfully, but these errors were encountered:
Azolo
changed the title
handle_disconnect does not handle initial connect error
Can't find how to trigger handle_disconnect during process initilization.
Mar 4, 2018
thank you and sorry! may be it could be true by default, i could not imagine application that will not start because of connection timeout - it may be a temporary network glitch.
It seems it's not working. I am trying this options to handle initial connection failure but no luck. What am I doing wrong here? [{:name, global_name()}, {:handle_initial_conn_failure, true}]
handle_disconnect works perfectly for infinite reconnection like in issue 5 - when host got down after some time
but it does not handle connection error in WebSockex.start_link - so if there is no connection to host, application does not start:
21:18:29.799 [info] Application arbi exited: Arbi.Application.start(:normal, []) returned an error: shutdown: failed to start child: Arbi.WsSup ** (EXIT) shutdown: failed to start child: Arbi.WsWorker ** (EXIT) %WebSockex.ConnError{original: :econnrefused}
The text was updated successfully, but these errors were encountered: