Repository navigation
Can't find how to trigger handle_disconnect during process initilization. #52
Description
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}
Activity
Azolo commentedon Mar 4, 2018
Hi, it's actually an option for
startandstart_link.Though it does need to be easier to find.
[-]handle_disconnect does not handle initial connect error[/-][+]Can't find how to trigger handle_disconnect during process initilization.[/+]artempankov commentedon Mar 5, 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.
vipul2774 commentedon Mar 5, 2022
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}]