默认
发表评论 2
想开发IM:买成品怕坑?租第3方怕贵?找开源自已撸?尽量别走弯路了... 找站长给点建议
[已回复] APP闪退后MobileIMSDK出现不能够正常登录的情况
阅读(41559) | 评论(2 收藏 淘帖
正常登录是没有问题的,但是当APP出现Bug闪退时,再次登录,就会收不到Server的推送消息。
Log如下:
[05 11:09:22,205 INFO ] [NioDatagramAcceptor-1] server.ServerCoreHandler - [IMCORE]与{uid:null,cid:-1}/192.168.1.176:14344的会话建立(sessionCreated)了...
[05 11:09:22,205 DEBUG] [pool-2-thread-16] filterchain.IoFilterEvent - Firing a SESSION_OPENED event for session 14
[05 11:09:22,205 INFO ] [pool-2-thread-16] server.ServerCoreHandler - [IMCORE]与{uid:null,cid:-1}/192.168.1.176:14344的会话(sessionOpened)打开了...
[05 11:09:22,205 DEBUG] [pool-2-thread-16] filterchain.IoFilterEvent - Event SESSION_OPENED has been fired for session 14
[05 11:09:22,205 DEBUG] [pool-2-thread-17] filterchain.IoFilterEvent - Firing a MESSAGE_RECEIVED event for session 14
[05 11:09:22,205 DEBUG] [pool-2-thread-17] server.ServerCoreHandler - +++++++++++jsonStr+++++++++++{"QoS":false,"dataContent":"{\"loginName\":\"6326cd87148946529366fc90f710c8c2\",\"loginPsw\":\"111111\"}","from":"-1","to":"0","type":0}
[05 11:09:22,205 INFO ] [pool-2-thread-17] server.ServerCoreHandler - [IMCORE]>> 客户端{uid:null,cid:-1}/192.168.1.176:14344发过来的登陆信息内容是:getLoginName=6326cd87148946529366fc90f710c8c2|getLoginPsw=111111
[05 11:09:22,205 DEBUG] [pool-2-thread-17] listener.ServerEventListenerImpl -  ++ 正在调用回调方法:OnVerifyUserCallBack...(extra=null)
[05 11:09:22,205 DEBUG] [pool-2-thread-17] listener.ServerEventListenerImpl - ++  lpUserName 6326cd87148946529366fc90f710c8c2 +lpPassword+111111
[05 11:09:22,205 DEBUG] [pool-2-thread-17] support.DefaultListableBeanFactory - Returning cached instance of singleton bean 'LoginBo'
[05 11:09:22,205 DEBUG] [pool-2-thread-17] spring.SqlSessionUtils - Creating a new SqlSession
[05 11:09:22,205 DEBUG] [pool-2-thread-17] spring.SqlSessionUtils - SqlSession [org.apache.ibatis.session.defaults.DefaultSqlSession@459ebf87] was not registered for synchronization because synchronization is not active
[05 11:09:22,205 DEBUG] [pool-2-thread-17] datasource.DataSourceUtils - Fetching JDBC Connection from DataSource
[05 11:09:22,205 DEBUG] [pool-2-thread-17] transaction.SpringManagedTransaction - JDBC Connection [com.alibaba.druid.proxy.jdbc.ConnectionProxyImpl@32b7ba66] will not be managed by Spring
[05 11:09:22,205 DEBUG] [pool-2-thread-17] UserMapper.selectByExample - ==>  Preparing: select 'true' as QUERYID, USER_ID, USER_MOBILE, USER_NAME, USER_PW, USER_GENDER, EMAIL, QQ, WECHAT, SIGN, GROUP_LOGO, OTHER_LOGO, HEAD_PHOTO, PROVINCE, CITY, COMPANY, COMPANY_INTRODUCE, POST, ACTIVE_FLG, ACCOUNT_FREEZE, ACCOUNT_PROTECT, ACCOUNT_STATE, IMPORT_CONTACTS_STATUS, DEL_FLG, INS_DATE, INS_USER, UPD_DATE, UPD_USER from USER WHERE ( USER_ID = ? and ACTIVE_FLG = ? and DEL_FLG = ? )
[05 11:09:22,205 DEBUG] [pool-2-thread-17] UserMapper.selectByExample - ==> Parameters: 6326cd87148946529366fc90f710c8c2(String), 0(String), 0(String)
[05 11:09:22,205 DEBUG] [pool-2-thread-17] UserMapper.selectByExample - <==      Total: 1
[05 11:09:22,205 DEBUG] [pool-2-thread-17] pool.PreparedStatementPool - {conn-10008, pstmt-20125} exit cache
[05 11:09:22,205 DEBUG] [pool-2-thread-17] pool.PreparedStatementPool - {conn-10008, pstmt-20178} enter cache
[05 11:09:22,205 DEBUG] [pool-2-thread-17] spring.SqlSessionUtils - Closing non transactional SqlSession [org.apache.ibatis.session.defaults.DefaultSqlSession@459ebf87]
[05 11:09:22,205 DEBUG] [pool-2-thread-17] datasource.DataSourceUtils - Returning JDBC Connection to DataSource
[05 11:09:22,205 DEBUG] [pool-2-thread-17] listener.ServerEventListenerImpl - ++  msgResponse null
[05 11:09:22,205 DEBUG] [pool-2-thread-17] listener.ServerEventListenerImpl - ++   SUCCESS 0
[05 11:09:22,205 DEBUG] [pool-2-thread-17] processor.UserProcessor - 【@】当前在线用户共(1)人------------------->
[05 11:09:22,205 DEBUG] [pool-2-thread-16] filterchain.IoFilterEvent - Firing a MESSAGE_SENT event for session 14
[05 11:09:22,205 DEBUG] [pool-2-thread-16] filterchain.IoFilterEvent - Event MESSAGE_SENT has been fired for session 14
[05 11:09:22,205 DEBUG] [pool-2-thread-17] listener.ServerEventListenerImpl - 正在调用回调方法:OnUserLoginAction_CallBack...
[05 11:09:22,205 DEBUG] [pool-2-thread-17] filterchain.IoFilterEvent - Event MESSAGE_RECEIVED has been fired for session 14
[05 11:09:24,672 DEBUG] [AWT-EventQueue-0] qos.QoS4SendDaemonS2C - 【IMCORE】【QoS发送方】=========== 消息发送质量保证线程运行中, 当前需要处理的列表长度为1...
[05 11:09:24,672 DEBUG] [AWT-EventQueue-0] qos.QoS4SendDaemonS2C - 【IMCORE】【QoS发送方】指纹为076984d0-14d0-4579-b5b1-6fb6a13a7835的消息包已成功进行重传,此次之后重传次数已达1(最多1次).
[05 11:09:24,672 DEBUG] [pool-2-thread-17] filterchain.IoFilterEvent - Firing a MESSAGE_SENT event for session 14
[05 11:09:24,672 DEBUG] [pool-2-thread-17] filterchain.IoFilterEvent - Event MESSAGE_SENT has been fired for session 14
[05 11:09:29,680 DEBUG] [AWT-EventQueue-0] qos.QoS4SendDaemonS2C - 【IMCORE】【QoS发送方】=========== 消息发送质量保证线程运行中, 当前需要处理的列表长度为1...
[05 11:09:29,680 DEBUG] [AWT-EventQueue-0] qos.QoS4SendDaemonS2C - 【IMCORE】【QoS发送方】指纹为076984d0-14d0-4579-b5b1-6fb6a13a7835的消息包重传次数已达1(最多1次)上限,将判定为丢包!
[05 11:09:29,680 WARN ] [AWT-EventQueue-0] qos.QoS4SendDaemonS2C - 【IMCORE】【QoS发送方】指纹为076984d0-14d0-4579-b5b1-6fb6a13a7835的消息已成功从发送质量保证队列中移除(可能是收到接收方的应答也可能是达到了重传的次数上限),重试次数=1
[05 11:09:29,680 DEBUG] [AWT-EventQueue-0] listener.MessageQoSEventS2CListnerImpl - 【DEBUG_QoS_S2C事件】收到系统的未实时送达事件通知,当前共有1个包QoS保证机制结束,判定为【无法实时送达】!
[05 11:09:33,051 DEBUG] [pool-2-thread-17] filterchain.IoFilterEvent - Firing a SESSION_CLOSED event for session 14
[05 11:09:33,051 INFO ] [pool-2-thread-17] server.ServerCoreHandler - [IMCORE]与{uid:6326cd87148946529366fc90f710c8c2,cid:6326cd87148946529366fc90f710c8c2}/192.168.1.176:14344的会话关闭(user_id=6326cd87148946529366fc90f710c8c2,loginName=6326cd87148946529366fc90f710c8c2)了...
[05 11:09:33,051 DEBUG] [pool-2-thread-17] listener.ServerEventListenerImpl - 正在调用回调方法:OnUserLogoutAction_CallBack...
[05 11:09:33,051 DEBUG] [pool-2-thread-17] filterchain.IoFilterEvent - Event SESSION_CLOSED has been fired for session 14
[05 11:09:34,690 DEBUG] [AWT-EventQueue-0] qos.QoS4SendDaemonS2C - 【IMCORE】【QoS发送方】=========== 消息发送质量保证线程运行中, 当前需要处理的列表长度为0...


和正常登录时候的Log比对了一下,发现有一处Log不一样
上面的异常Log
[05 11:09:22,205 DEBUG] [pool-2-thread-17] processor.UserProcessor - 【@】当前在线用户共(1)人------------------->
[05 11:09:22,205 DEBUG] [pool-2-thread-16] filterchain.IoFilterEvent - Firing a MESSAGE_SENT event for session 14
[05 11:09:22,205 DEBUG] [pool-2-thread-16] filterchain.IoFilterEvent - Event MESSAGE_SENT has been fired for session 14
[05 11:09:22,205 DEBUG] [pool-2-thread-17] listener.ServerEventListenerImpl - 正在调用回调方法:OnUserLoginAction_CallBack...
[05 11:09:22,205 DEBUG] [pool-2-thread-17] filterchain.IoFilterEvent - Event MESSAGE_RECEIVED has been fired for session 14
[05 11:09:24,672 DEBUG] [AWT-EventQueue-0] qos.QoS4SendDaemonS2C - 【IMCORE】【QoS发送方】=========== 消息发送质量保证线程运行中, 当前需要处理的列表长度为1...
[05 11:09:24,672 DEBUG] [AWT-EventQueue-0] qos.QoS4SendDaemonS2C - 【IMCORE】【QoS发送方】指纹为076984d0-14d0-4579-b5b1-6fb6a13a7835的消息包已成功进行重传,此次之后重传次数已达1(最多1次).


正常登录的Log
[05 11:42:26,402 DEBUG] [pool-2-thread-19] processor.UserProcessor - 【@】当前在线用户共(1)人------------------->
[05 11:42:26,402 DEBUG] [pool-2-thread-18] filterchain.IoFilterEvent - Firing a MESSAGE_SENT event for session 15
[05 11:42:26,402 DEBUG] [pool-2-thread-18] filterchain.IoFilterEvent - Event MESSAGE_SENT has been fired for session 15
[05 11:42:26,402 DEBUG] [pool-2-thread-19] listener.ServerEventListenerImpl - 正在调用回调方法:OnUserLoginAction_CallBack...
[05 11:42:26,402 DEBUG] [pool-2-thread-19] filterchain.IoFilterEvent - Event MESSAGE_RECEIVED has been fired for session 15
[05 11:42:26,481 DEBUG] [pool-2-thread-19] filterchain.IoFilterEvent - Firing a MESSAGE_RECEIVED event for session 15
[05 11:42:26,481 DEBUG] [pool-2-thread-19] server.ServerCoreHandler - +++++++++++jsonStr+++++++++++{"QoS":false,"dataContent":"2169e7be-f8e1-4750-8d8b-2e6d7e053241","from":"6326cd87148946529366fc90f710c8c2","to":"0","type":4}
[05 11:42:26,481 INFO ] [pool-2-thread-19] server.ServerCoreHandler - >> 收到客户端{uid:6326cd87148946529366fc90f710c8c2,cid:6326cd87148946529366fc90f710c8c2}/192.168.1.176:25009的通用数据发送请求.
[05 11:42:26,481 DEBUG] [pool-2-thread-19] server.ServerCoreHandler - 【IMCORE】【QoS机制_S2C】收到6326cd87148946529366fc90f710c8c2发过来的指纹为2169e7be-f8e1-4750-8d8b-2e6d7e053241的应答包.
[05 11:42:26,481 DEBUG] [pool-2-thread-19] listener.MessageQoSEventS2CListnerImpl - 【DEBUG_QoS_S2C事件】收到对方已收到消息事件的通知,fp=2169e7be-f8e1-4750-8d8b-2e6d7e053241
[05 11:42:26,481 WARN ] [pool-2-thread-19] qos.QoS4SendDaemonS2C - 【IMCORE】【QoS发送方】指纹为2169e7be-f8e1-4750-8d8b-2e6d7e053241的消息已成功从发送质量保证队列中移除(可能是收到接收方的应答也可能是达到了重传的次数上限),重试次数=0


这是什么问题呢?

即时通讯网 - 即时通讯开发者社区! 来源: - 即时通讯开发者社区!

标签:MobileIMSDK
上一篇:[已回复] 求教我的MobileIMSDK服务端在centos 6.5 上出现JSON解析异常下一篇:[已回复] MobileIMSDK udp压力测试丢包严重?
推荐方案
评论 2
引用:JackJiang 发表于 2016-11-05 21:19
服务端的log显示,服务端回复给你的登陆连接包已成功被收到了。。

看错了,我把正常的log看成了你说的有问题的了。。。

服务问确实显示送出的登陆包,没有收到客户端应答。

这个问题就有点奇怪了,客户端的Logcat中输出的Log有没有不正常的情况存在?

毫无疑问客户端是能够发送数据到服务端,不然连接请求服务端就不会收到,你确定客户端有没有收到服务端的应答。。。如果客户端没有收到,那就意味着服务端到客户端这条路不通,需要再找原因。。。
服务端的log显示,服务端回复给你的登陆连接包已成功被收到了。。
打赏楼主 ×
使用微信打赏! 使用支付宝打赏!

返回顶部