RTC服务端SDK使用大批量出现 onConnectionLost 问题,导致服务有问题

本地使用java处理房间的音频流数据,依赖

<dependency>    
<groupId>io.agora.rtc</groupId>  
  <artifactId>linux-sdk</artifactId>
      <version>4.0.1</version>
      </dependency>
      <dependency>  
        <groupId>io.agora</groupId>
            <artifactId>authentication</artifactId>
                <version>2.0.0</version>
                </dependency>

应用在linux端接受房间流数据做处理时,刚开始都正常,过段时间经常会出现本地用户加入到房间以后,一定时间以后就会出现 onConnectionLost 请求,然后可能要5分钟左右才会重连成功,这个问题有遇到的吗?怎么解决?

我在出现这个 onConnectionLost 请求以后,然后关闭这个连接,重新创建连接,也是一直没有 onConnected 的回调

这个问题是批量出现的,因为我是在linux里面,用java在后台多线程,用多个用户连接了多个不同的房间,接受房间里面用户的音频流数据做业务判断。

有遇到的帮忙解决下吗?这个问题一出现,然后我们这边的容器就重启了,目前发现so文件有报错


报错日志如下:


2023-11-23T11:54:59.615436989+08:00 stdout F _fn_RtcConnObserver_on_user_left: attach jvm result is 0
2023-11-23T11:54:59.615439909+08:00 stdout F _fn_RtcConnObserver_on_user_left: attach jvm result is 0
2023-11-23T11:54:59.615442755+08:00 stdout F _fn_RtcConnObserver_on_user_left: attach jvm result is 0
2023-11-23T11:54:59.615445289+08:00 stdout F _fn_RtcConnObserver_on_reconnecting: attach jvm result is 0
2023-11-23T11:54:59.615448856+08:00 stdout F _fn_RtcConnObserver_on_content_inspect_result: attach jvm result is 0
2023-11-23T11:54:59.649771187+08:00 stdout F #
2023-11-23T11:54:59.649799602+08:00 stdout F # A fatal error has been detected by the Java Runtime Environment:
2023-11-23T11:54:59.649804614+08:00 stdout F #
2023-11-23T11:54:59.649813785+08:00 stdout F #  SIGSEGV (0xb) at pc=0x00007fe706158995, pid=6, tid=101
2023-11-23T11:54:59.649818031+08:00 stdout F #
2023-11-23T11:54:59.649820932+08:00 stdout F # JRE version: OpenJDK Runtime Environment Temurin-17.0.1+12 (17.0.1+12) (build 17.0.1+12)
2023-11-23T11:54:59.649825737+08:00 stdout F # Java VM: OpenJDK 64-Bit Server VM Temurin-17.0.1+12 (17.0.1+12, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-amd64)
2023-11-23T11:54:59.649829705+08:00 stdout F # Problematic frame:
2023-11-23T11:54:59.649855275+08:00 stdout F # C  [libagora_rtc_sdk.so+0xb27995]
2023-11-23T11:54:59.649867921+08:00 stdout F #
2023-11-23T11:54:59.649872364+08:00 stdout F # Core dump will be written. Default location: /qke/log/core.%h.%e.%t.6
2023-11-23T11:54:59.649877047+08:00 stdout F #
2023-11-23T11:54:59.64999669+08:00 stdout F # An error report file with more information is saved as:
2023-11-23T11:54:59.650004562+08:00 stdout F # /app/hs_err_pid6.log
2023-11-23T11:54:59.704245475+08:00 stdout F #
2023-11-23T11:54:59.70426977+08:00 stdout F # If you would like to submit a bug report, please visit:
2023-11-23T11:54:59.704274956+08:00 stdout F #   https://github.com/adoptium/adoptium-support/issues
2023-11-23T11:54:59.704278866+08:00 stdout F # The crash happened outside the Java Virtual Machine in native code.
2023-11-23T11:54:59.704284967+08:00 stdout F # See problematic frame for where to report the bug.
2023-11-23T11:54:59.704288173+08:00 stdout F #
2023-11-23T11:54:59.704291725+08:00 stdout F _fn_RtcConnObserver_on_reconnecting: attach jvm result is 0
2023-11-23T11:54:59.704295193+08:00 stdout F _fn_RtcConnObserver_on_content_inspect_result: attach jvm result is 0