erlang - why gen_tcp:controlling_process() can failed with badarg? -
I have a problem with ejabberd module, it is http_bind but when I debug deeply, I found that socket and spelling After accepting the Hilling Process and when the GN_TPP: the process of re-signing for the receiver data for the new process received by the controlling process failed in Berang, why?
...
{ok, socket} = get_tcp: accept (summons), opts = [{active, false}, ...],% here proc_lib Function Return result: spawn_link (handler, ..) {OK, PID} = ejabberd_http: start ({gen_tcp, socket}, opts), gen_tcp: controling_process (socket, pid): {badarg, [erlang, Port_connect, [# port & lt; 0.140743856 & gt;, & lt; 0.5939.4350 & gt;]}, {inet, tcp_controlling_process, 2}, {ejabberd_socket, start, 4}, {ejabberd_listener, accept, 3}, {proc_lib, init_p, 5}]}
Any help? Most probably have crashed before calling for controlling the socket or process.
Why did they get crashed, I do not know, you have ensured that there is a process of ebbird, should it run?
Comments
Post a Comment