taosadapter一直崩溃

Tdengine用的版本是tdengine-tsdb-oss-3.3.7.5，后端服务是Java服务，4个读线程1个写线程，用的是websocket高效写入的连接方式，配置参数如下 driver-class-name: com.taosdata.jdbc.ws.WebSocketDriver url: jdbc:TAOS-WS://.../*** username: root password: taosdata

# --- Hikari 连接池参数 ---
# HikariCP 会自动识别这些 `hikari.*` 前缀的属性
hikari:
  maximum-pool-size: 10
  minimum-idle: 5
  connection-timeout: 30000
  idle-timeout: 600000
  max-lifetime: 1800000
  data-source-properties:
    # --- TDengine 专用参数 ---
    # 异步写入模式
    asyncWrite: "stmt"
    # 单次写入请求中批处理的最大行数
    batchSizeByRow: "10000"
    # 每个后端写线程队列中缓存的最大行数
    cacheSizeByRow: "100000"
    # 后端写线程数量
    backendWriteThreadNum: "5"
    # 连接断开时自动重连
    enableAutoReconnect: "true"
    # 等待服务端处理写请求的最长时间（毫秒）
    messageWaitTimeout: "5000"
    # 在调用 `addBatch` 后修改二进制数据时是否复制数据
    copyData: "false"
    # 是否检查子表名长度和可变长数据类型长度
    strictCheck: "false"

正常查询的时候没有什么稳定，taosadapter也是正常启动的，但是如果并发高了一点，就会出现taosadapter一直崩溃重启，甚至直接起不来的情况 ● taosadapter.service - taosAdapter - RESTful and WebSocket gateway for accessing TDengine Loaded: loaded (/etc/systemd/system/taosadapter.service; enabled; vendor preset: disabled) Active: active (running) since Sat 2025-10-11 11:20:17 CST; 1min 41s ago Main PID: 63516 (taosadapter) ● taosadapter.service - taosAdapter - RESTful and WebSocket gateway for accessing TDengine Loaded: loaded (/etc/systemd/system/taosadapter.service; enabled; vendor preset: disabled) Active: failed (Result: start-limit) since Sat 2025-10-11 11:24:52 CST; 40s ago Process: 11653 ExecStart=/usr/bin/taosadapter (code=killed, signal=SEGV) Main PID: 11653 (code=killed, signal=SEGV)

taosadapter一条ERROR 10/11 11:24:51.349353 00011653 WSC ERROR SID:0x3, QID:0x1bd01d14bce01e7d result is nil, result_id:4, action:fetch_raw_block

taoslog报错 10/11 11:24:51.851143 00011661 C QRY INFO QID:0x1bd01d14bd00209f init with pTrans:0x2 10/11 11:24:51.858444 00011853 C QRY INFO stmt2:0x7fab1810a3c0, stmt2 bind thread stopped 10/11 11:24:51.858828 00011661 C TSC ERROR taos_fetch_raw_block_a res is NULL

taoskeeper报错 2025/10/11 11:25:03 [Recovery] 2025/10/11 - 11:25:03 panic recovered: runtime error: invalid memory address or nil pointer dereference /root/.gvm/gos/go1.24.2/src/runtime/panic.go:262 (0x47daf8) /root/.gvm/gos/go1.24.2/src/runtime/signal_unix.go:925 (0x47dac8) /data/release/main/TDinternal/community/tools/keeper/api/gen_metric.go:303 (0xb89b0e) /data/release/main/TDinternal/community/tools/keeper/api/gen_metric.go:262 (0xb88fbc) /data/release/main/TDinternal/community/tools/keeper/api/gen_metric.go:217 (0xb885e4) /root/.gvm/pkgsets/go1.24.2/global/pkg/mod/github.com/gin-gonic/gin@v1.9.1/context.go:174 (0x95566e) /root/.gvm/pkgsets/go1.24.2/global/pkg/mod/github.com/gin-gonic/gin@v1.9.1/recovery.go:102 (0x95565b) /data/release/main/TDinternal/community/tools/keeper/infrastructure/log/web.go:53 (0xa9817b) /root/.gvm/pkgsets/go1.24.2/global/pkg/mod/github.com/gin-gonic/gin@v1.9.1/context.go:174 (0xa97b86) /data/release/main/TDinternal/community/tools/keeper/infrastructure/log/web.go:24 (0xa97b6d) /root/.gvm/pkgsets/go1.24.2/global/pkg/mod/github.com/gin-gonic/gin@v1.9.1/context.go:174 (0x9544ad) /root/.gvm/pkgsets/go1.24.2/global/pkg/mod/github.com/gin-gonic/gin@v1.9.1/gin.go:620 (0x954144) /root/.gvm/pkgsets/go1.24.2/global/pkg/mod/github.com/gin-gonic/gin@v1.9.1/gin.go:576 (0x953c89) /root/.gvm/gos/go1.24.2/src/net/http/server.go:3301 (0x71c44d) /root/.gvm/gos/go1.24.2/src/net/http/server.go:2102 (0x6f9e84) /root/.gvm/gos/go1.24.2/src/runtime/asm_amd64.s:1700 (0x483880)  10/11 11:25:15.450355 00049429 DB ERROR QID:0x4000000000002240 latency:553.79µs, sql:insert into km_hadoop02_6043 using keeper_monitor tags ('hadoop02:6043') values ( now, 0.013333, 0.031563, 0), err:Post "http://192.168.183.102:6041/rest/sql/log?req_id=3329599474764884630": dial tcp 192.168.183.102:6041: connect: connection refused 10/11 11:25:15.450396 00049429 MON ERROR execute sql:insert into km_hadoop02_6043 using keeper_monitor tags ('hadoop02:6043') values ( now, 0.013333, 0.031563, 0), error:Post "http://192.168.183.102:6041/rest/sql/log?req_id=3329599474764884630": dial tcp 192.168.183.102:6041: connect: connection refused 10/11 11:25:30.450727 00049429 DB ERROR QID:0x4000000000002242 latency:537.824µs, sql:insert into km_hadoop02_6043 using keeper_monitor tags ('hadoop02:6043') values ( now, 0.006667, 0.031563, 0), err:Post "http://192.168.183.102:6041/rest/sql/log?req_id=3329599474825702039": dial tcp 192.168.183.102:6041: connect: connection refused 10/11 11:25:30.450770 00049429 MON ERROR execute sql:insert into km_hadoop02_6043 using keeper_monitor tags ('hadoop02:6043') values ( now, 0.006667, 0.031563, 0), error:Post "http://192.168.183.102:6041/rest/sql/log?req_id=3329599474825702039": dial tcp 192.168.183.102:6041: connect: connection refused 10/11 11:25:33.613538 00049429 DB ERROR QID:0x1000000053fc500 latency:410.897µs, sql:insert into log.taosd_cluster_basic_838192438401933312 using taosd_cluster_basic tags ('838192438401933312') values (1760153133612, '192.168.183.102:6030', 1, '3.3.7.5') , err:Post "http://192.168.183.102:6041/rest/sql/log?req_id=3329599474839333528": dial tcp 192.168.183.102:6041: connect: connection refused 10/11 11:25:33.613633 00049429 GEN ERROR QID:0x1000000053fc500 insert taosd_cluster_basic error, msg:Post "http://192.168.183.102:6041/rest/sql/log?req_id=3329599474839333528": dial tcp 192.168.183.102:6041: connect: connection refused 10/11 11:25:33.615016 00049429 WEB ERROR

请问这个是什么问题导致taosadapter一直崩溃的，该怎么修复或者怎么排查