但我使用 mqtt.js 通 ws 端口发送消息时 ,会造成emqx 重新连接

环境为 docker搭建的 emqx 服务器.启用了内置的数据库用户管理.
问题1: 在我使用 mqtt.js 在网页端,通过 ws 端口以 10hz 的频率发送消息时 , emqx 桌面端会频繁的重新连接 .
问题2: 大疆无人机在使用 ws 连接消息服务器时 , 只能工作 10秒左右 , 然后在 eqmx 的管理页面可以看到无人机的客户端已经下线 .
感觉这两个问题可能有关联 , 是否是 emqx 服务器配置问题?

麻烦提供一下 emqx 的版本及日志

emqx 为通过docker 安装的 5.8版本,
以下为中断时的客户端连接日志
{
“time”: “2024-10-18T03:42:36.122763+00:00”,
“msg”: " crasher:\n initial call: cowboy_clear:connection_process/4\n pid: <0.49143.0>\n registered_name: \n exception error: no match of right hand side value 15459\n in function emqx_ws_connection:handle_outgoing/2 (emqx_ws_connection.erl, line 814)\n in call from emqx_ws_connection:websocket_info/2 (emqx_ws_connection.erl, line 998)\n in call from cowboy_websocket:handler_call/6 (cowboy_websocket.erl, line 487)\n ancestors: [<0.3096.0>,<0.3095.0>,ranch_sup,<0.2523.0>]\n message_queue_len: 1\n messages: [{deliver,<<"thing/product/7CTD8Y22/drc/down">>,\n {message,<<0,6,36,184,24,9,119,216,185,70,0,0,191,\n 241,0,103>>,\n 0,\n <<"a1559e7c-8dd8-4780-b952-100cc4797da2">>,\n #{dup => false,retain => false},\n #{peername => {{172,17,0,1},59008},\n protocol => mqtt,\n username => <<"nc-dji">>,\n peerhost => {172,17,0,1},\n properties => #{},proto_ver => 4,\n client_attrs => #{}},\n <<"thing/product/7CTD8Y22/drc/down">>,\n <<"{\"method\":\"heart_beat\",\"data\":{\"seq\":44,\"timestamp\":1729222955969}}">>,\n 1729222956120,#{}}}]\n links: [#Port<0.4340>,<0.3096.0>]\n dictionary: [{‘recv_msg.qos0’,44},\n {{#{action_type => subscribe,qos => 0},\n <<"thing/product/7CTD8Y22/ping">>},\n {allow,1729222909850}},\n {‘$logger_metadata$’,\n #{peername => "172.17.0.1:59010",\n username => <<"7CTD8Y22">>,\n clientid => <<"7CTD8Y22-1729222909242">>}},\n {send_oct,15459},\n {‘recv_msg.qos1’,1125},\n {send_cnt,1229},\n {{#{retain => false,action_type => publish,qos => 1},\n <<"thing/product/7CTD8Y22/drc/up">>},\n {allow,1729222911054}},\n {recv_oct,668817},\n {send_pkt,1229},\n {recv_cnt,1172},\n {send_msg,101},\n {{#{action_type => subscribe,qos => 0},\n <<"thing/product/7CTD8Y22/drc/down">>},\n {allow,1729222909750}},\n {incoming_pubs,56},\n {‘send_msg.qos0’,101},\n {authz_keys_q,\n {[{#{retain => false,action_type => publish,qos => 1},\n <<"thing/product/7CTD8Y22/drc/up">>},\n {#{retain => false,action_type => publish,qos => 0},\n <<"thing/product/7CTD8Y22/drc/up">>},\n {#{action_type => subscribe,qos => 0},\n <<"thing/product/7CTD8Y22/ping">>}],\n [{#{action_type => subscribe,qos => 0},\n <<"thing/product/7CTD8Y22/drc/down">>}]}},\n {guid,{1729222956114440,203710298898423,1170}},\n {authz_cache_size,4},\n {incoming_bytes,31736},\n {{#{retain => false,action_type => publish,qos => 0},\n <<"thing/product/7CTD8Y22/drc/up">>},\n {allow,1729222911013}},\n {outgoing_pubs,0},\n {recv_msg,1169},\n {recv_pkt,1172},\n {outgoing_bytes,0}]\n trap_exit: true\n status: running\n heap_size: 6772\n stack_size: 28\n reductions: 5347138\n neighbours:\n",
“meta”: {
“username”: “7CTD8Y22",
“time”: 1729222956120873,
“report_cb”: “fun proc_lib:report_cb/2”,
“pid”: “<0.49143.0>”,
“peername”: “172.17.0.1:59010”,
“mfa”: “{proc_lib,crash_report,4}”,
“logger_formatter”: {
“title”: “CRASH REPORT”
},
“line”: 584,
“gl”: “<0.2522.0>”,
“file”: “proc_lib.erl”,
“error_logger”: {
“type”: “crash_report”,
“tag”: “error_report”
},
“domain”: [
“otp”,
“sasl”
],
“clientid”: "7CTD
8Y22-1729222909242”
},
“level”: “error”
}

https://github.com/emqx/emqx/issues/13943

不好意思,这个问题是 5.8.0 引入的,已经在 5.8.1 上修复了。麻烦更新一下哈