IM后台日志经常有ERROR_CODE_INVALID_DATA 是为啥

lizq 27天前 45

29/09/2021 17:44:23,569 [epollEventLoopGroup-3-11] INFO  ProtocolProcessor 605  - Processing connection lost event. CId=c15ce71b5234a3281610862086029 29/09/2021 17:44:23,570 [epollEventLoopGroup-3-11] INFO  MessageMetricsHandler 72  - channel<18888228985> closing after read 5 messages and wrote 5 messages 29/09/2021 17:44:23,570 [epollEventLoopGroup-3-11] INFO  BytesMetricsHandler 73  - channel<18888228985> closing after read 168 bytes and wrote 0 bytes 29/09/2021 17:44:23,592 [epollEventLoopGroup-3-5] INFO  ProtocolProcessor 472  - Processing PUBLISH message. CId=4d0fa48fff64f2cf1626828651444, topic=GMUT, messageId=22, qos=AT_LEAST_ONCE 29/09/2021 17:44:23,593 [epollEventLoopGroup-3-5] INFO  Qos1PublishHandler 152  - imHandler fromUser=13081079333, topic=GMUT 29/09/2021 17:44:23,593 [pool-2-thread-12] INFO  IMHandler 156  - imHandler fromUser=13081079333, clientId=4d0fa48fff64f2cf1626828651444, topic=GMUT 29/09/2021 17:44:23,593 [pool-2-thread-12] ERROR IMHandler 37  - Exception: null 29/09/2021 17:44:23,593 [pool-2-thread-12] ERROR IMHandler 38  -  sun.reflect.GeneratedMethodAccessor36.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) java.lang.reflect.Method.invoke(Unknown Source) io.moquette.imhandler.IMHandler.getDataObject(IMHandler.java:110) io.moquette.imhandler.IMHandler.lambda$doHandler$0(IMHandler.java:191) cn.wildfirechat.server.ThreadPoolExecutorWrapper.lambda$execute$0(ThreadPoolExecutorWrapper.java:37) java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) java.util.concurrent.FutureTask.run(Unknown Source) java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source) java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) java.lang.Thread.run(Unknown Source) 29/09/2021 17:44:23,593 [pool-2-thread-12] INFO  ConnectionDescriptorStore 53  - Sending PUBACK message CId=<4d0fa48fff64f2cf1626828651444>, messageId=22, errorCode=ERROR_CODE_INVALID_DATA

最新回复 (3)
  • HeavyRain 20天前
    引用 2
    可以看一下客户端请求,如果客户端没有异常可以忽略不计。另外检查一下客户端版本,是不是升级到最新能够避免这种情况
  • lizq 15天前
    引用 3
    HeavyRain 可以看一下客户端请求,如果客户端没有异常可以忽略不计。另外检查一下客户端版本,是不是升级到最新能够避免这种情况
    当前的情况是客户端反馈有时候会发送异常,返回的错误码为:public static final int INVALID_DATA = 2;  //"invalid data");后台的日志中找到了上述的错误日志。且已知后台server的版本是v0.38,而app端sdk的版本是v0.8.9。 app端的异常现象并不是必现的,属于偶发现象。
  • HeavyRain 15天前
    引用 4
    0.38太旧了,现在都0.7x了,查了好几十个版本了,能升级一下吗
返回