Sockets erlang套接字(使用ranch)在短时间内关闭?
我使用ranch来监听套接字,但在大约5秒钟的短时间内,ranch关闭了套接字,并且我的套接字设置在上面,那么怎么了Sockets erlang套接字(使用ranch)在短时间内关闭?,sockets,erlang,ranch,Sockets,Erlang,Ranch,我使用ranch来监听套接字,但在大约5秒钟的短时间内,ranch关闭了套接字,并且我的套接字设置在上面,那么怎么了 {ok, _} = ranch:start_listener(server,200, ranch_tcp, [{port, 5555},{active, once}, {max_connections, 1024}], server_protocol, []), %% start the listener 协议文件在下面,ranch侦听接受套接字,并反向接收数据,
{ok, _} = ranch:start_listener(server,200, ranch_tcp, [{port, 5555},{active, once}, {max_connections, 1024}], server_protocol, []), %% start the listener
协议文件在下面,ranch侦听接受套接字,并反向接收数据,但问题是,当将数据发送回客户端时,大约五秒钟后,客户端收到消息说服务器关闭了套接字,我不知道ranch的默认设置是否导致了这一情况
-module(reverse_protocol).
-behaviour(gen_server).
-behaviour(ranch_protocol).
%% API.
-export([start_link/4]).
%% gen_server.
-export([init/1]).
-export([init/4]).
-export([handle_call/3]).
-export([handle_cast/2]).
-export([handle_info/2]).
-export([terminate/2]).
-export([code_change/3]).
-define(TIMEOUT, 5000).
-record(state, {socket, transport}).
%% API.
start_link(Ref, Socket, Transport, Opts) ->
proc_lib:start_link(?MODULE, init, [Ref, Socket, Transport, Opts]).
%% gen_server.
%% This function is never called. We only define it so that
%% we can use the -behaviour(gen_server) attribute.
init([]) -> {ok, undefined}.
init(Ref, Socket, Transport, _Opts = []) ->
ok = proc_lib:init_ack({ok, self()}),
ok = ranch:accept_ack(Ref),
ok = Transport:setopts(Socket, [{active, once}]),
gen_server:enter_loop(?MODULE, [],
#state{socket=Socket, transport=Transport},
?TIMEOUT).
handle_info({tcp, Socket, Data}, State=#state{
socket=Socket, transport=Transport}) ->
Transport:setopts(Socket, [{active, once}]),
Transport:send(Socket, reverse_binary(Data)),
{noreply, State, ?TIMEOUT};
handle_info({tcp_closed, _Socket}, State) ->
{stop, normal, State};
handle_info({tcp_error, _, Reason}, State) ->
{stop, Reason, State};
handle_info(timeout, State) ->
{stop, normal, State};
handle_info(_Info, State) ->
{stop, normal, State}.
handle_call(_Request, _From, State) ->
{reply, ok, State}.
handle_cast(_Msg, State) ->
{noreply, State}.
terminate(_Reason, _State) ->
ok.
code_change(_OldVsn, State, _Extra) ->
{ok, State}.
%% Internal.
reverse_binary(B) when is_binary(B) ->
[list_to_binary(lists:reverse(binary_to_list(
binary:part(B, {0, byte_size(B)-2})
))), "\r\n"].
因此,您的问题是因为gen_服务器进程超时并关闭。关闭套接字是一个副作用,因为ranch将套接字链接到生成的处理程序进程 一旦新进程通过调用
gen_server:enter_loop
进入gen_server循环,它就有超时时间
毫秒来接收消息,然后再发送超时
消息
-define(TIMEOUT, 5000).
init(Ref, Socket, Transport, _Opts = []) ->
ok = proc_lib:init_ack({ok, self()}),
ok = ranch:accept_ack(Ref),
ok = Transport:setopts(Socket, [{active, once}]),
gen_server:enter_loop(?MODULE, [],
#state{socket=Socket, transport=Transport},
?TIMEOUT). %% timeout because of this!
handle_info({tcp, Socket, Data}, State=#state{
socket=Socket, transport=Transport}) ->
Transport:setopts(Socket, [{active, once}]),
Transport:send(Socket, reverse_binary(Data)),
{noreply, State, ?TIMEOUT}; %% timeout because of this!
因此,当这五秒钟过去,gen_服务器在这段时间内没有收到任何消息时,它会向自己发送一条超时
消息,然后由处理信息
handle_info(timeout, State) ->
{stop, normal, State};
您的handle\u info
告诉gen\u服务器停止,这会导致套接字关闭,因为两者链接在一起
您可以完全删除超时,也可以停止导致进程关闭的超时
下面是我如何更改句柄信息
超时代码:
handle_info(timeout, State) ->
io:format("the socket is idle~n"),
{noreply,State};
您是如何确定ranch关闭了侦听套接字的?客户端打印出原因,我还尝试连接到python套接字服务器,它工作正常@evnu您能提供一个显示问题的最小示例吗?好的,我立即将此添加到问题描述中。@evnu我为这个问题添加了更多细节,谢谢您给我一个建议。@evnu