请选择 进入手机版 | 继续访问电脑版

默认
发表评论 18
[已回复] MobileIMSDK android端未登录直接发送消息 系统崩溃
1.问题如题目 MobileIMSDK android端未登录直接发送消息 系统崩溃
2.发送消息后  运行一段时间出现一下日志
D/LocalUDPDataReciever: 【IMCORE】收到服务端回过来的Keep Alive心跳响应包.
D/QoS4SendDaemon: 【IMCORE】【QoS】=========== 消息发送质量保证线程运行中, 当前需要处理的列表长度为0...
D/KeepAliveDaemon: 【IMCORE】心跳线程执行中...
D/LocalUDPSocketProvider: 【IMCORE】isLocalUDPSocketReady()==true,直接返回本地socket引用哦。
D/LocalUDPSocketProvider: 【IMCORE】isLocalUDPSocketReady()==true,直接返回本地socket引用哦。
W/zygote: Long monitor contention with owner Thread-7 (18927) at void java.net.DatagramSocket.receive(java.net.DatagramPacket)(DatagramSocket.java:-1) waiters=2 in void java.net.DatagramSocket.receive(java.net.DatagramPacket) for 9.070s
W/zygote: Current owner stack:
W/zygote:     at java.net.DatagramPacket.<init>(DatagramPacket.java:78)
W/zygote:     at java.net.DatagramPacket.<init>(DatagramPacket.java:95)
W/zygote:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever.p2pListeningImpl(LocalUDPDataReciever.java:106)
W/zygote:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever.access$100(LocalUDPDataReciever.java:36)
W/zygote:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever$1.run(LocalUDPDataReciever.java:85)
W/zygote:     at java.lang.Thread.run(Thread.java:764)
W/zygote: Contender stack:
W/zygote:     at java.net.DatagramSocket.receive(DatagramSocket.java:-1)
W/zygote:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever.p2pListeningImpl(LocalUDPDataReciever.java:110)
W/zygote:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever.access$100(LocalUDPDataReciever.java:36)
W/zygote:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever$1.run(LocalUDPDataReciever.java:85)
W/zygote:     at java.lang.Thread.run(Thread.java:764)
D/LocalUDPDataReciever: 【IMCORE】收到服务端回过来的Keep Alive心跳响应包.
D/KeepAliveDaemon: 【IMCORE】心跳线程执行中...
D/LocalUDPSocketProvider: 【IMCORE】isLocalUDPSocketReady()==true,直接返回本地socket引用哦。

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

标签:MobileIMSDK
上一篇:[已回复] MobileIMSDK能改造成使用Protobuf作为传输的数据格式吗?下一篇:[已回复] 关于如何准备MobileIMSDK压力测试数据样本的疑惑

本帖已收录至以下技术专辑

推荐方案
评论 18
是的,未登陆就发消息肯定是不允许的,因为有些初始化工作是在你登陆成功后才进行,否则就会出现你贴出来的异常。

你一定要照着demo的顺序来初始化和使用,否则肯定用不了。im的底层算法并不是简单的像Http短连接一样,连调随用,算法是有上下文关系的,复杂的多
签名: 《新浪微博技术分享:微博实时直播答题的百万高并发架构实践》http://www.52im.net/thread-2022-1-1.html
引用:JackJiang 发表于 2018-07-17 16:53
是的,未登陆就发消息肯定是不允许的,因为有些初始化工作是在你登陆成功后才进行,否则就会出现你贴出来的 ...

后面日志是 我登陆后  发送消息,一段时间后出现的日志,大约在五分钟左右出现的
引用:cha8511995 发表于 2018-07-18 15:56
后面日志是 我登陆后  发送消息,一段时间后出现的日志,大约在五分钟左右出现的

界面上是什么表现?手机型号是什么?android版本具体是多少?
签名: 《新浪微博技术分享:微博实时直播答题的百万高并发架构实践》http://www.52im.net/thread-2022-1-1.html
引用:JackJiang 发表于 2018-07-18 16:36
界面上是什么表现?手机型号是什么?android版本具体是多少?

我将登陆按钮放到后面main界面,点击登陆,登陆成功,然后发送消息
一段时间后 控制台出现日志信息 大约时间在五分钟左右
界面上面没有任何变化, android版本是8.1 手机是红米
引用:cha8511995 发表于 2018-07-19 17:09
我将登陆按钮放到后面main界面,点击登陆,登陆成功,然后发送消息
一段时间后 控制台出现日志信息 大约 ...

屏幕锁屏了吗?这个问题以前没有听说过,很有可能跟手机的省电策略、安全设置什么的有关。你可以把日志贴的全一点,比如从app登陆到这个异常出现的所有log,以及服务端的Log。这样的可以全面分析一下到底是什么原因导致的
签名: 《新浪微博技术分享:微博实时直播答题的百万高并发架构实践》http://www.52im.net/thread-2022-1-1.html
引用:JackJiang 发表于 2018-07-19 21:13
屏幕锁屏了吗?这个问题以前没有听说过,很有可能跟手机的省电策略、安全设置什么的有关。你可以把日志贴 ...

刚才测试了,这问题现在未出现了
引用:cha8511995 发表于 2018-07-20 09:49
刚才测试了,这问题现在未出现了

好,你持续观察,如果复现,你就保留好详细的各端日志
签名: 《新浪微博技术分享:微博实时直播答题的百万高并发架构实践》http://www.52im.net/thread-2022-1-1.html
引用:JackJiang 发表于 2018-07-20 09:50
好,你持续观察,如果复现,你就保留好详细的各端日志


07-20 09:46:51.604 32255-689/net.openmob.mobileimsdk.android.demo W/zygote: Long monitor contention with owner Thread-13 (507) at void java.net.DatagramSocket.receive(java.net.DatagramPacket)(DatagramSocket.java:-1) waiters=10 in void java.net.DatagramSocket.receive(java.net.DatagramPacket) for 1.716s
07-20 09:46:51.615 32255-32255/net.openmob.mobileimsdk.android.demo D/ViewRootImpl[Toast]: hardware acceleration = true , fakeHwAccelerated = false, sRendererDisabled = false, forceHwAccelerated = false, sSystemRendererDisabled = false
07-20 09:46:51.624 32255-32255/net.openmob.mobileimsdk.android.demo I/Toast: Show toast from OpPackageName:net.openmob.mobileimsdk.android.demo, PackageName:net.openmob.mobileimsdk.android.demo
07-20 09:46:51.624 32255-32255/net.openmob.mobileimsdk.android.demo D/LocalUDPDataReciever: 【IMCORE】【QoS】向5ae92b198a9b591904a0eab1发送add742ec-dd17-4358-be6d-9bf46c963b30包的应答包成功,from=5ae92b198a9b591904a0eab1!
07-20 09:46:51.625 32255-32255/net.openmob.mobileimsdk.android.demo W/QoS4SendDaemon: 【IMCORE】【QoS】指纹为add742ec-dd17-4358-be6d-9bf46c963b30的消息已成功从发送质量保证队列中移除(可能是收到接收方的应答也可能是达到了重传的次数上限),重试次数=0
07-20 09:46:51.675 32255-32275/net.openmob.mobileimsdk.android.demo D/Surface: Surface::connect(this=0x8ec33800,api=1)
07-20 09:46:51.675 32255-32255/net.openmob.mobileimsdk.android.demo D/Surface: Surface::allocateBuffers(this=0x8ec33800)
07-20 09:46:51.741 32255-32275/net.openmob.mobileimsdk.android.demo D/Surface: Surface::connect(this=0x8c844800,api=1)
07-20 09:46:51.741 32255-32255/net.openmob.mobileimsdk.android.demo D/Surface: Surface::allocateBuffers(this=0x8c844800)
07-20 09:46:51.757 32255-860/net.openmob.mobileimsdk.android.demo D/LocalUDPDataReciever: 【IMCORE】本地UDP端口侦听中,端口=7801...
07-20 09:46:51.758 32255-860/net.openmob.mobileimsdk.android.demo D/LocalUDPSocketProvider: 【IMCORE】isLocalUDPSocketReady()==true,直接返回本地socket引用哦。
07-20 09:46:51.789 32255-32255/net.openmob.mobileimsdk.android.demo I/ChatBaseEventImpl: 【DEBUG_UI】IM服务器登录/重连成功!
07-20 09:46:51.791 32255-32255/net.openmob.mobileimsdk.android.demo I/System.out: 登陆成功
07-20 09:46:51.793 32255-32332/net.openmob.mobileimsdk.android.demo D/LocalUDPSocketProvider: 【IMCORE】isLocalUDPSocketReady()==true,直接返回本地socket引用哦。
07-20 09:46:51.799 32255-32275/net.openmob.mobileimsdk.android.demo D/GraphicBuffer: register, handle(0x8f39e700) (w:640 h:218 s:640 f:0x1 u:b00)
07-20 09:46:51.818 32255-32275/net.openmob.mobileimsdk.android.demo D/GraphicBuffer: register, handle(0x8f39e700) (w:640 h:218 s:640 f:0x1 u:b00)
07-20 09:46:51.880 32255-32255/net.openmob.mobileimsdk.android.demo D/QoS4ReciveDaemon: 【IMCORE】【QoS接收方】++++++++++ START 暂存处理线程正在运行中,当前长度92.
07-20 09:46:51.881 32255-32339/net.openmob.mobileimsdk.android.demo D/QoS4SendDaemon: 【IMCORE】【QoS】=========== 消息发送质量保证线程运行中, 当前需要处理的列表长度为0...
07-20 09:46:51.881 32255-32255/net.openmob.mobileimsdk.android.demo D/QoS4ReciveDaemon: 【IMCORE】【QoS接收方】++++++++++ END 暂存处理线程正在运行中,当前长度92.
引用:cha8511995 发表于 2018-07-20 09:57
07-20 09:46:51.604 32255-689/net.openmob.mobileimsdk.android.demo W/zygote: Long monitor content ...


07-20 09:46:51.882 32255-32255/net.openmob.mobileimsdk.android.demo D/LocalUDPDataReciever: 【IMCORE】【QoS】向0发送d809bb37-3b37-44f0-9b53-d4cfd301850d包的应答包成功,from=5ae92b198a9b591904a0eab1!
07-20 09:46:51.915 32255-32333/net.openmob.mobileimsdk.android.demo D/LocalUDPSocketProvider: 【IMCORE】isLocalUDPSocketReady()==true,直接返回本地socket引用哦。
07-20 09:46:51.926 32255-395/net.openmob.mobileimsdk.android.demo D/LocalUDPSocketProvider: 【IMCORE】isLocalUDPSocketReady()==true,直接返回本地socket引用哦。
07-20 09:46:51.926 32255-507/net.openmob.mobileimsdk.android.demo W/zygote: Long monitor contention with owner Thread-11 (391) at void java.net.DatagramSocket.receive(java.net.DatagramPacket)(DatagramSocket.java:-1) waiters=10 in void java.net.DatagramSocket.receive(java.net.DatagramPacket) for 2.022s
07-20 09:46:51.927 32255-378/net.openmob.mobileimsdk.android.demo W/zygote: Long monitor contention with owner Thread-11 (391) at void java.net.DatagramSocket.receive(java.net.DatagramPacket)(DatagramSocket.java:-1) waiters=10 in void java.net.DatagramSocket.receive(java.net.DatagramPacket) for 2.021s
07-20 09:46:51.927 32255-395/net.openmob.mobileimsdk.android.demo D/LocalUDPSocketProvider: 【IMCORE】isLocalUDPSocketReady()==true,直接返回本地socket引用哦。
07-20 09:46:51.929 32255-32255/net.openmob.mobileimsdk.android.demo D/MainActivity: 2数据已成功发出!
07-20 09:46:51.943 32255-32255/net.openmob.mobileimsdk.android.demo D/ChatTransDataEventImpl: 【DEBUG_UI】[typeu=1]收到来自用户5ae92b198a9b591904a0eab1的消息:{"sourceTime":1530845390664,"messageTime":1530845391664,"messageId":"5b513f484916f127f8322d49","messageType":1,"messageBody":"一二三四五六七八九十","bDestory":false}
07-20 09:46:51.964 32255-32330/net.openmob.mobileimsdk.android.demo D/LocalUDPSocketProvider: 【IMCORE】isLocalUDPSocketReady()==true,直接返回本地socket引用哦。
07-20 09:46:51.979 32255-32255/net.openmob.mobileimsdk.android.demo D/LocalUDPDataReciever: 【IMCORE】【QoS】收到5ae92b198a9b591904a0eab1发过来的指纹为bc83c79e-69bf-4ab8-a518-ff47fef2ef7b的应答包.
07-20 09:46:51.979 32255-32255/net.openmob.mobileimsdk.android.demo D/MessageQoSEventImpl: 【DEBUG_UI】收到对方已收到消息事件的通知,fp=bc83c79e-69bf-4ab8-a518-ff47fef2ef7b
07-20 09:46:52.033 32255-32255/net.openmob.mobileimsdk.android.demo D/ViewRootImpl[Toast]: hardware acceleration = true , fakeHwAccelerated = false, sRendererDisabled = false, forceHwAccelerated = false, sSystemRendererDisabled = false
07-20 09:46:52.042 32255-32255/net.openmob.mobileimsdk.android.demo I/Toast: Show toast from OpPackageName:net.openmob.mobileimsdk.android.demo, PackageName:net.openmob.mobileimsdk.android.demo
07-20 09:46:52.042 32255-32255/net.openmob.mobileimsdk.android.demo D/LocalUDPDataReciever: 【IMCORE】【QoS】向5ae92b198a9b591904a0eab1发送bc83c79e-69bf-4ab8-a518-ff47fef2ef7b包的应答包成功,from=5ae92b198a9b591904a0eab1!
07-20 09:46:52.043 32255-32255/net.openmob.mobileimsdk.android.demo W/QoS4SendDaemon: 【IMCORE】【QoS】指纹为bc83c79e-69bf-4ab8-a518-ff47fef2ef7b的消息已成功从发送质量保证队列中移除(可能是收到接收方的应答也可能是达到了重传的次数上限),重试次数=0
07-20 09:46:52.082 32255-32255/net.openmob.mobileimsdk.android.demo D/Surface: Surface::allocateBuffers(this=0x8ed66000)
07-20 09:46:52.082 32255-32275/net.openmob.mobileimsdk.android.demo D/Surface: Surface::connect(this=0x8ed66000,api=1)
07-20 09:46:52.106 32255-32275/net.openmob.mobileimsdk.android.demo D/GraphicBuffer: register, handle(0x8f39e700) (w:640 h:218 s:640 f:0x1 u:b00)
07-20 09:46:52.114 32255-32339/net.openmob.mobileimsdk.android.demo D/LocalUDPSocketProvider: 【IMCORE】isLocalUDPSocketReady()==true,直接返回本地socket引用哦。
07-20 09:46:52.121 32255-395/net.openmob.mobileimsdk.android.demo D/LocalUDPSocketProvider: 【IMCORE】isLocalUDPSocketReady()==true,直接返回本地socket引用哦。
07-20 09:46:52.121 32255-391/net.openmob.mobileimsdk.android.demo W/zygote: Long monitor contention with owner Thread-10 (379) at void java.net.DatagramSocket.receive(java.net.DatagramPacket)(DatagramSocket.java:-1) waiters=10 in void java.net.DatagramSocket.receive(java.net.DatagramPacket) for 2.204s
07-20 09:46:52.122 32255-379/net.openmob.mobileimsdk.android.demo W/zygote: Long monitor contention with owner Thread-12 (395) at void java.net.DatagramSocket.receive(java.net.DatagramPacket)(DatagramSocket.java:-1) waiters=10 in void java.net.DatagramSocket.receive(java.net.DatagramPacket) for 2.204s
07-20 09:46:52.122 32255-395/net.openmob.mobileimsdk.android.demo D/LocalUDPSocketProvider: 【IMCORE】isLocalUDPSocketReady()==true,直接返回本地socket引用哦。
07-20 09:46:52.137 32255-32255/net.openmob.mobileimsdk.android.demo D/MainActivity: 2数据已成功发出!
07-20 09:46:52.154 32255-32255/net.openmob.mobileimsdk.android.demo D/ChatTransDataEventImpl: 【DEBUG_UI】[typeu=1]收到来自用户5ae92b198a9b591904a0eab1的消息:{"sourceTime":1530845390664,"messageTime":1530845391664,"messageId":"5b513f494916f127f8322d4a","messageType":1,"messageBody":"一二三四五六七八九十","bDestory":false}
07-20 09:46:52.173 32255-32333/net.openmob.mobileimsdk.android.demo D/LocalUDPSocketProvider: 【IMCORE】isLocalUDPSocketReady()==true,直接返回本地socket引用哦。
07-20 09:46:52.191 32255-32255/net.openmob.mobileimsdk.android.demo D/LocalUDPDataReciever: 【IMCORE】【QoS】收到5ae92b198a9b591904a0eab1发过来的指纹为fe5e3e77-5436-43e8-bd79-10a4f68bae38的应答包.
07-20 09:46:52.192 32255-32255/net.openmob.mobileimsdk.android.demo D/MessageQoSEventImpl: 【DEBUG_UI】收到对方已收到消息事件的通知,fp=fe5e3e77-5436-43e8-bd79-10a4f68bae38
07-20 09:46:52.234 32255-32255/net.openmob.mobileimsdk.android.demo D/ViewRootImpl[Toast]: hardware acceleration = true , fakeHwAccelerated = false, sRendererDisabled = false, forceHwAccelerated = false, sSystemRendererDisabled = false
07-20 09:46:52.243 32255-32255/net.openmob.mobileimsdk.android.demo I/Toast: Show toast from OpPackageName:net.openmob.mobileimsdk.android.demo, PackageName:net.openmob.mobileimsdk.android.demo
07-20 09:46:52.244 32255-32255/net.openmob.mobileimsdk.android.demo D/LocalUDPDataReciever: 【IMCORE】【QoS】向5ae92b198a9b591904a0eab1发送fe5e3e77-5436-43e8-bd79-10a4f68bae38包的应答包成功,from=5ae92b198a9b591904a0eab1!
07-20 09:46:52.245 32255-32255/net.openmob.mobileimsdk.android.demo W/QoS4SendDaemon: 【IMCORE】【QoS】指纹为fe5e3e77-5436-43e8-bd79-10a4f68bae38的消息已成功从发送质量保证队列中移除(可能是收到接收方的应答也可能是达到了重传的次数上限),重试次数=0
07-20 09:46:52.298 32255-32255/net.openmob.mobileimsdk.android.demo D/Surface: Surface::allocateBuffers(this=0x8f712800)
引用:cha8511995 发表于 2018-07-20 09:57
07-20 09:46:51.882 32255-32255/net.openmob.mobileimsdk.android.demo D/LocalUDPDataReciever: 【IM ...


07-20 09:46:52.298 32255-32275/net.openmob.mobileimsdk.android.demo D/Surface: Surface::connect(this=0x8f712800,api=1)
07-20 09:46:52.320 32255-32275/net.openmob.mobileimsdk.android.demo D/GraphicBuffer: register, handle(0x8f39e700) (w:640 h:218 s:640 f:0x1 u:b00)
07-20 09:46:54.172 32255-32275/net.openmob.mobileimsdk.android.demo D/Surface: Surface::disconnect(this=0x8f712800,api=1)
07-20 09:46:54.173 32255-32275/net.openmob.mobileimsdk.android.demo D/GraphicBuffer: unregister, handle(0x8fe9b580) (w:640 h:218 s:640 f:0x1 u:b00)
07-20 09:46:54.176 32255-32255/net.openmob.mobileimsdk.android.demo D/View: [Warning] assignParent to null: this = android.widget.LinearLayout{3f55445 V.E...... ......ID 0,0-640,218}
07-20 09:46:54.783 32255-32332/net.openmob.mobileimsdk.android.demo D/KeepAliveDaemon: 【IMCORE】心跳线程执行中...
07-20 09:46:54.797 32255-32332/net.openmob.mobileimsdk.android.demo D/LocalUDPSocketProvider: 【IMCORE】isLocalUDPSocketReady()==true,直接返回本地socket引用哦。
07-20 09:46:54.810 32255-395/net.openmob.mobileimsdk.android.demo D/LocalUDPSocketProvider: 【IMCORE】isLocalUDPSocketReady()==true,直接返回本地socket引用哦。
07-20 09:46:54.810 32255-513/net.openmob.mobileimsdk.android.demo W/zygote: Long monitor contention with owner Thread-12 (395) at void java.net.DatagramSocket.receive(java.net.DatagramPacket)(DatagramSocket.java:-1) waiters=10 in void java.net.DatagramSocket.receive(java.net.DatagramPacket) for 4.498s
07-20 09:46:54.819 32255-32255/net.openmob.mobileimsdk.android.demo D/LocalUDPDataReciever: 【IMCORE】收到服务端回过来的Keep Alive心跳响应包.
07-20 09:46:56.911 32255-32339/net.openmob.mobileimsdk.android.demo D/QoS4SendDaemon: 【IMCORE】【QoS】=========== 消息发送质量保证线程运行中, 当前需要处理的列表长度为0...
07-20 09:46:57.803 32255-32333/net.openmob.mobileimsdk.android.demo D/KeepAliveDaemon: 【IMCORE】心跳线程执行中...
07-20 09:46:57.858 32255-32333/net.openmob.mobileimsdk.android.demo D/LocalUDPSocketProvider: 【IMCORE】isLocalUDPSocketReady()==true,直接返回本地socket引用哦。
07-20 09:46:57.886 32255-395/net.openmob.mobileimsdk.android.demo D/LocalUDPSocketProvider: 【IMCORE】isLocalUDPSocketReady()==true,直接返回本地socket引用哦。
07-20 09:46:57.888 32255-774/net.openmob.mobileimsdk.android.demo W/zygote: Long monitor contention with owner Thread-12 (395) at void java.net.DatagramSocket.receive(java.net.DatagramPacket)(DatagramSocket.java:-1) waiters=10 in void java.net.DatagramSocket.receive(java.net.DatagramPacket) for 7.570s
07-20 09:46:57.888 32255-774/net.openmob.mobileimsdk.android.demo W/zygote: Current owner stack:
07-20 09:46:57.889 32255-774/net.openmob.mobileimsdk.android.demo W/zygote:     at android.os.MessageQueue.nativeWake(Native method)
07-20 09:46:57.889 32255-774/net.openmob.mobileimsdk.android.demo W/zygote:     at android.os.MessageQueue.enqueueMessage(MessageQueue.java:589)
07-20 09:46:57.889 32255-774/net.openmob.mobileimsdk.android.demo W/zygote:   - locked <0x0180179a> (a android.os.MessageQueue)
07-20 09:46:57.890 32255-774/net.openmob.mobileimsdk.android.demo W/zygote:     at android.os.Handler.enqueueMessage(Handler.java:662)
07-20 09:46:57.890 32255-774/net.openmob.mobileimsdk.android.demo W/zygote:     at android.os.Handler.sendMessageAtTime(Handler.java:631)
07-20 09:46:57.890 32255-774/net.openmob.mobileimsdk.android.demo W/zygote:     at android.os.Handler.sendMessageDelayed(Handler.java:601)
07-20 09:46:57.890 32255-774/net.openmob.mobileimsdk.android.demo W/zygote:     at android.os.Handler.sendMessage(Handler.java:538)
07-20 09:46:57.891 32255-774/net.openmob.mobileimsdk.android.demo W/zygote:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever.p2pListeningImpl(LocalUDPDataReciever.java:113)
07-20 09:46:57.891 32255-774/net.openmob.mobileimsdk.android.demo W/zygote:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever.access$100(LocalUDPDataReciever.java:36)
07-20 09:46:57.891 32255-774/net.openmob.mobileimsdk.android.demo W/zygote:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever$1.run(LocalUDPDataReciever.java:85)
07-20 09:46:57.891 32255-774/net.openmob.mobileimsdk.android.demo W/zygote:     at java.lang.Thread.run(Thread.java:764)
07-20 09:46:57.892 32255-774/net.openmob.mobileimsdk.android.demo W/zygote: Contender stack:
07-20 09:46:57.892 32255-774/net.openmob.mobileimsdk.android.demo W/zygote:     at java.net.DatagramSocket.receive(DatagramSocket.java:-1)
07-20 09:46:57.892 32255-774/net.openmob.mobileimsdk.android.demo W/zygote:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever.p2pListeningImpl(LocalUDPDataReciever.java:110)
07-20 09:46:57.892 32255-774/net.openmob.mobileimsdk.android.demo W/zygote:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever.access$100(LocalUDPDataReciever.java:36)
07-20 09:46:57.893 32255-774/net.openmob.mobileimsdk.android.demo W/zygote:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever$1.run(LocalUDPDataReciever.java:85)
07-20 09:46:57.893 32255-774/net.openmob.mobileimsdk.android.demo W/zygote:     at java.lang.Thread.run(Thread.java:764)
07-20 09:46:57.923 32255-32255/net.openmob.mobileimsdk.android.demo D/LocalUDPDataReciever: 【IMCORE】收到服务端回过来的Keep Alive心跳响应包.
引用:cha8511995 发表于 2018-07-20 09:57
07-20 09:46:51.882 32255-32255/net.openmob.mobileimsdk.android.demo D/LocalUDPDataReciever: 【IM ...


07-20 09:47:00.865 32255-32330/net.openmob.mobileimsdk.android.demo D/KeepAliveDaemon: 【IMCORE】心跳线程执行中...
07-20 09:47:00.901 32255-32330/net.openmob.mobileimsdk.android.demo D/LocalUDPSocketProvider: 【IMCORE】isLocalUDPSocketReady()==true,直接返回本地socket引用哦。
07-20 09:47:00.924 32255-395/net.openmob.mobileimsdk.android.demo D/LocalUDPSocketProvider: 【IMCORE】isLocalUDPSocketReady()==true,直接返回本地socket引用哦。
07-20 09:47:00.925 32255-32331/net.openmob.mobileimsdk.android.demo W/zygote: Long monitor contention with owner Thread-12 (395) at void java.net.DatagramSocket.receive(java.net.DatagramPacket)(DatagramSocket.java:-1) waiters=10 in void java.net.DatagramSocket.receive(java.net.DatagramPacket) for 9.623s
07-20 09:47:00.926 32255-32331/net.openmob.mobileimsdk.android.demo W/zygote: Current owner stack:
07-20 09:47:00.926 32255-32331/net.openmob.mobileimsdk.android.demo W/zygote:     at android.os.MessageQueue.nativeWake(Native method)
07-20 09:47:00.926 32255-32331/net.openmob.mobileimsdk.android.demo W/zygote:     at android.os.MessageQueue.enqueueMessage(MessageQueue.java:589)
07-20 09:47:00.926 32255-32331/net.openmob.mobileimsdk.android.demo W/zygote:   - locked <0x0180179a> (a android.os.MessageQueue)
07-20 09:47:00.926 32255-32331/net.openmob.mobileimsdk.android.demo W/zygote:     at android.os.Handler.enqueueMessage(Handler.java:662)
07-20 09:47:00.926 32255-32331/net.openmob.mobileimsdk.android.demo W/zygote:     at android.os.Handler.sendMessageAtTime(Handler.java:631)
07-20 09:47:00.927 32255-32331/net.openmob.mobileimsdk.android.demo W/zygote:     at android.os.Handler.sendMessageDelayed(Handler.java:601)
07-20 09:47:00.927 32255-32331/net.openmob.mobileimsdk.android.demo W/zygote:     at android.os.Handler.sendMessage(Handler.java:538)
07-20 09:47:00.927 32255-32331/net.openmob.mobileimsdk.android.demo W/zygote:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever.p2pListeningImpl(LocalUDPDataReciever.java:113)
07-20 09:47:00.928 32255-32331/net.openmob.mobileimsdk.android.demo W/zygote:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever.access$100(LocalUDPDataReciever.java:36)
07-20 09:47:00.929 32255-32331/net.openmob.mobileimsdk.android.demo W/zygote:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever$1.run(LocalUDPDataReciever.java:85)
07-20 09:47:00.929 32255-32331/net.openmob.mobileimsdk.android.demo W/zygote:     at java.lang.Thread.run(Thread.java:764)
07-20 09:47:00.930 32255-32331/net.openmob.mobileimsdk.android.demo W/zygote: Contender stack:
07-20 09:47:00.931 32255-32331/net.openmob.mobileimsdk.android.demo W/zygote:     at java.net.DatagramSocket.receive(DatagramSocket.java:-1)
07-20 09:47:00.931 32255-32331/net.openmob.mobileimsdk.android.demo W/zygote:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever.p2pListeningImpl(LocalUDPDataReciever.java:110)
07-20 09:47:00.931 32255-32331/net.openmob.mobileimsdk.android.demo W/zygote:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever.access$100(LocalUDPDataReciever.java:36)
07-20 09:47:00.932 32255-32331/net.openmob.mobileimsdk.android.demo W/zygote:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever$1.run(LocalUDPDataReciever.java:85)
07-20 09:47:00.932 32255-32331/net.openmob.mobileimsdk.android.demo W/zygote:     at java.lang.Thread.run(Thread.java:764)
07-20 09:47:00.944 32255-32255/net.openmob.mobileimsdk.android.demo D/LocalUDPDataReciever: 【IMCORE】收到服务端回过来的Keep Alive心跳响应包.
07-20 09:47:01.918 32255-32332/net.openmob.mobileimsdk.android.demo D/QoS4SendDaemon: 【IMCORE】【QoS】=========== 消息发送质量保证线程运行中, 当前需要处理的列表长度为0...
07-20 09:47:03.906 32255-32339/net.openmob.mobileimsdk.android.demo D/KeepAliveDaemon: 【IMCORE】心跳线程执行中...
07-20 09:47:03.921 32255-32339/net.openmob.mobileimsdk.android.demo D/LocalUDPSocketProvider: 【IMCORE】isLocalUDPSocketReady()==true,直接返回本地socket引用哦。
07-20 09:47:03.936 32255-395/net.openmob.mobileimsdk.android.demo D/LocalUDPSocketProvider: 【IMCORE】isLocalUDPSocketReady()==true,直接返回本地socket引用哦。
07-20 09:47:03.936 32255-532/net.openmob.mobileimsdk.android.demo W/zygote: Long monitor contention with owner Thread-12 (395) at void java.net.DatagramSocket.receive(java.net.DatagramPacket)(DatagramSocket.java:-1) waiters=10 in void java.net.DatagramSocket.receive(java.net.DatagramPacket) for 12.634s
07-20 09:47:03.937 32255-532/net.openmob.mobileimsdk.android.demo W/zygote: Current owner stack:
07-20 09:47:03.937 32255-532/net.openmob.mobileimsdk.android.demo W/zygote:     at android.os.MessageQueue.nativeWake(Native method)
07-20 09:47:03.937 32255-532/net.openmob.mobileimsdk.android.demo W/zygote:     at android.os.MessageQueue.enqueueMessage(MessageQueue.java:589)
07-20 09:47:03.938 32255-532/net.openmob.mobileimsdk.android.demo W/zygote:   - locked <0x0180179a> (a android.os.MessageQueue)
07-20 09:47:03.938 32255-532/net.openmob.mobileimsdk.android.demo W/zygote:     at android.os.Handler.enqueueMessage(Handler.java:662)
07-20 09:47:03.938 32255-532/net.openmob.mobileimsdk.android.demo W/zygote:     at android.os.Handler.sendMessageAtTime(Handler.java:631)
07-20 09:47:03.938 32255-532/net.openmob.mobileimsdk.android.demo W/zygote:     at android.os.Handler.sendMessageDelayed(Handler.java:601)
07-20 09:47:03.939 32255-532/net.openmob.mobileimsdk.android.demo W/zygote:     at android.os.Handler.sendMessage(Handler.java:538)
07-20 09:47:03.939 32255-532/net.openmob.mobileimsdk.android.demo W/zygote:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever.p2pListeningImpl(LocalUDPDataReciever.java:113)
07-20 09:47:03.939 32255-532/net.openmob.mobileimsdk.android.demo W/zygote:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever.access$100(LocalUDPDataReciever.java:36)
07-20 09:47:03.939 32255-532/net.openmob.mobileimsdk.android.demo W/zygote:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever$1.run(LocalUDPDataReciever.java:85)
07-20 09:47:03.939 32255-532/net.openmob.mobileimsdk.android.demo W/zygote:     at java.lang.Thread.run(Thread.java:764)
07-20 09:47:03.939 32255-532/net.openmob.mobileimsdk.android.demo W/zygote: Contender stack:
07-20 09:47:03.939 32255-532/net.openmob.mobileimsdk.android.demo W/zygote:     at java.net.DatagramSocket.receive(DatagramSocket.java:-1)
07-20 09:47:03.940 32255-532/net.openmob.mobileimsdk.android.demo W/zygote:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever.p2pListeningImpl(LocalUDPDataReciever.java:110)
07-20 09:47:03.940 32255-532/net.openmob.mobileimsdk.android.demo W/zygote:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever.access$100(LocalUDPDataReciever.java:36)
07-20 09:47:03.940 32255-532/net.openmob.mobileimsdk.android.demo W/zygote:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever$1.run(LocalUDPDataReciever.java:85)
07-20 09:47:03.940 32255-532/net.openmob.mobileimsdk.android.demo W/zygote:     at java.lang.Thread.run(Thread.java:764)
07-20 09:47:03.954 32255-32255/net.openmob.mobileimsdk.android.demo D/LocalUDPDataReciever: 【IMCORE】收到服务端回过来的Keep Alive心跳响应包.
引用:cha8511995 发表于 2018-07-20 09:58
07-20 09:47:00.865 32255-32330/net.openmob.mobileimsdk.android.demo D/KeepAliveDaemon: 【IMCORE ...


07-20 09:47:06.923 32255-32333/net.openmob.mobileimsdk.android.demo D/QoS4SendDaemon: 【IMCORE】【QoS】=========== 消息发送质量保证线程运行中, 当前需要处理的列表长度为0...
07-20 09:47:06.926 32255-32333/net.openmob.mobileimsdk.android.demo D/KeepAliveDaemon: 【IMCORE】心跳线程执行中...
07-20 09:47:06.949 32255-32333/net.openmob.mobileimsdk.android.demo D/LocalUDPSocketProvider: 【IMCORE】isLocalUDPSocketReady()==true,直接返回本地socket引用哦。
07-20 09:47:06.971 32255-395/net.openmob.mobileimsdk.android.demo D/LocalUDPSocketProvider: 【IMCORE】isLocalUDPSocketReady()==true,直接返回本地socket引用哦。
07-20 09:47:06.972 32255-522/net.openmob.mobileimsdk.android.demo W/zygote: Long monitor contention with owner Thread-12 (395) at void java.net.DatagramSocket.receive(java.net.DatagramPacket)(DatagramSocket.java:-1) waiters=10 in void java.net.DatagramSocket.receive(java.net.DatagramPacket) for 15.643s
07-20 09:47:06.972 32255-522/net.openmob.mobileimsdk.android.demo W/zygote: Current owner stack:
07-20 09:47:06.972 32255-522/net.openmob.mobileimsdk.android.demo W/zygote:     at java.net.DatagramPacket.setData(DatagramPacket.java:279)
07-20 09:47:06.972 32255-522/net.openmob.mobileimsdk.android.demo W/zygote:   - locked <0x05d728cb> (a java.net.DatagramPacket)
07-20 09:47:06.972 32255-522/net.openmob.mobileimsdk.android.demo W/zygote:     at java.net.DatagramPacket.<init>(DatagramPacket.java:79)
07-20 09:47:06.972 32255-522/net.openmob.mobileimsdk.android.demo W/zygote:     at java.net.DatagramPacket.<init>(DatagramPacket.java:95)
07-20 09:47:06.972 32255-522/net.openmob.mobileimsdk.android.demo W/zygote:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever.p2pListeningImpl(LocalUDPDataReciever.java:106)
07-20 09:47:06.972 32255-522/net.openmob.mobileimsdk.android.demo W/zygote:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever.access$100(LocalUDPDataReciever.java:36)
07-20 09:47:06.973 32255-522/net.openmob.mobileimsdk.android.demo W/zygote:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever$1.run(LocalUDPDataReciever.java:85)
07-20 09:47:06.973 32255-522/net.openmob.mobileimsdk.android.demo W/zygote:     at java.lang.Thread.run(Thread.java:764)
07-20 09:47:06.973 32255-522/net.openmob.mobileimsdk.android.demo W/zygote: Contender stack:
07-20 09:47:06.973 32255-522/net.openmob.mobileimsdk.android.demo W/zygote:     at java.net.DatagramSocket.receive(DatagramSocket.java:-1)
07-20 09:47:06.973 32255-522/net.openmob.mobileimsdk.android.demo W/zygote:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever.p2pListeningImpl(LocalUDPDataReciever.java:110)
07-20 09:47:06.973 32255-522/net.openmob.mobileimsdk.android.demo W/zygote:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever.access$100(LocalUDPDataReciever.java:36)
07-20 09:47:06.973 32255-522/net.openmob.mobileimsdk.android.demo W/zygote:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever$1.run(LocalUDPDataReciever.java:85)
07-20 09:47:06.973 32255-522/net.openmob.mobileimsdk.android.demo W/zygote:     at java.lang.Thread.run(Thread.java:764)
07-20 09:47:06.993 32255-32255/net.openmob.mobileimsdk.android.demo D/LocalUDPDataReciever: 【IMCORE】收到服务端回过来的Keep Alive心跳响应包.
07-20 09:47:09.954 32255-32332/net.openmob.mobileimsdk.android.demo D/KeepAliveDaemon: 【IMCORE】心跳线程执行中...
07-20 09:47:09.978 32255-32332/net.openmob.mobileimsdk.android.demo D/LocalUDPSocketProvider: 【IMCORE】isLocalUDPSocketReady()==true,直接返回本地socket引用哦。
07-20 09:47:10.001 32255-395/net.openmob.mobileimsdk.android.demo D/LocalUDPSocketProvider: 【IMCORE】isLocalUDPSocketReady()==true,直接返回本地socket引用哦。
07-20 09:47:10.003 32255-368/net.openmob.mobileimsdk.android.demo W/zygote: Long monitor contention with owner Thread-12 (395) at void java.net.DatagramSocket.receive(java.net.DatagramPacket)(DatagramSocket.java:-1) waiters=10 in void java.net.DatagramSocket.receive(java.net.DatagramPacket) for 18.671s
07-20 09:47:10.003 32255-368/net.openmob.mobileimsdk.android.demo W/zygote: Current owner stack:
07-20 09:47:10.004 32255-368/net.openmob.mobileimsdk.android.demo W/zygote:     at android.os.MessageQueue.nativeWake(Native method)
07-20 09:47:10.004 32255-368/net.openmob.mobileimsdk.android.demo W/zygote:     at android.os.MessageQueue.enqueueMessage(MessageQueue.java:589)
07-20 09:47:10.004 32255-368/net.openmob.mobileimsdk.android.demo W/zygote:   - locked <0x0180179a> (a android.os.MessageQueue)
07-20 09:47:10.004 32255-368/net.openmob.mobileimsdk.android.demo W/zygote:     at android.os.Handler.enqueueMessage(Handler.java:662)
07-20 09:47:10.005 32255-368/net.openmob.mobileimsdk.android.demo W/zygote:     at android.os.Handler.sendMessageAtTime(Handler.java:631)
07-20 09:47:10.005 32255-368/net.openmob.mobileimsdk.android.demo W/zygote:     at android.os.Handler.sendMessageDelayed(Handler.java:601)
07-20 09:47:10.005 32255-368/net.openmob.mobileimsdk.android.demo W/zygote:     at android.os.Handler.sendMessage(Handler.java:538)
07-20 09:47:10.006 32255-368/net.openmob.mobileimsdk.android.demo W/zygote:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever.p2pListeningImpl(LocalUDPDataReciever.java:113)
07-20 09:47:10.006 32255-368/net.openmob.mobileimsdk.android.demo W/zygote:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever.access$100(LocalUDPDataReciever.java:36)
07-20 09:47:10.006 32255-368/net.openmob.mobileimsdk.android.demo W/zygote:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever$1.run(LocalUDPDataReciever.java:85)
07-20 09:47:10.006 32255-368/net.openmob.mobileimsdk.android.demo W/zygote:     at java.lang.Thread.run(Thread.java:764)
07-20 09:47:10.007 32255-368/net.openmob.mobileimsdk.android.demo W/zygote: Contender stack:
07-20 09:47:10.007 32255-368/net.openmob.mobileimsdk.android.demo W/zygote:     at java.net.DatagramSocket.receive(DatagramSocket.java:-1)
07-20 09:47:10.007 32255-368/net.openmob.mobileimsdk.android.demo W/zygote:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever.p2pListeningImpl(LocalUDPDataReciever.java:110)
07-20 09:47:10.007 32255-368/net.openmob.mobileimsdk.android.demo W/zygote:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever.access$100(LocalUDPDataReciever.java:36)
07-20 09:47:10.008 32255-368/net.openmob.mobileimsdk.android.demo W/zygote:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever$1.run(LocalUDPDataReciever.java:85)
07-20 09:47:10.008 32255-368/net.openmob.mobileimsdk.android.demo W/zygote:     at java.lang.Thread.run(Thread.java:764)
07-20 09:47:10.039 32255-32255/net.openmob.mobileimsdk.android.demo D/LocalUDPDataReciever: 【IMCORE】收到服务端回过来的Keep Alive心跳响应包.
07-20 09:47:11.928 32255-32339/net.openmob.mobileimsdk.android.demo D/QoS4SendDaemon: 【IMCORE】【QoS】=========== 消息发送质量保证线程运行中, 当前需要处理的列表长度为0...
07-20 09:47:12.994 32255-32330/net.openmob.mobileimsdk.android.demo D/KeepAliveDaemon: 【IMCORE】心跳线程执行中...
07-20 09:47:13.007 32255-32330/net.openmob.mobileimsdk.android.demo D/LocalUDPSocketProvider: 【IMCORE】isLocalUDPSocketReady()==true,直接返回本地socket引用哦。
07-20 09:47:13.023 32255-395/net.openmob.mobileimsdk.android.demo D/LocalUDPSocketProvider: 【IMCORE】isLocalUDPSocketReady()==true,直接返回本地socket引用哦。
引用:cha8511995 发表于 2018-07-20 09:58
07-20 09:47:00.865 32255-32330/net.openmob.mobileimsdk.android.demo D/KeepAliveDaemon: 【IMCORE ...


07-20 09:47:13.024 32255-689/net.openmob.mobileimsdk.android.demo W/zygote: Long monitor contention with owner Thread-12 (395) at void java.net.DatagramSocket.receive(java.net.DatagramPacket)(DatagramSocket.java:-1) waiters=10 in void java.net.DatagramSocket.receive(java.net.DatagramPacket) for 21.416s
07-20 09:47:13.024 32255-689/net.openmob.mobileimsdk.android.demo W/zygote: Current owner stack:
07-20 09:47:13.025 32255-689/net.openmob.mobileimsdk.android.demo W/zygote:     at android.os.MessageQueue.nativeWake(Native method)
07-20 09:47:13.025 32255-689/net.openmob.mobileimsdk.android.demo W/zygote:     at android.os.MessageQueue.enqueueMessage(MessageQueue.java:589)
07-20 09:47:13.026 32255-689/net.openmob.mobileimsdk.android.demo W/zygote:   - locked <0x0180179a> (a android.os.MessageQueue)
07-20 09:47:13.026 32255-689/net.openmob.mobileimsdk.android.demo W/zygote:     at android.os.Handler.enqueueMessage(Handler.java:662)
07-20 09:47:13.026 32255-689/net.openmob.mobileimsdk.android.demo W/zygote:     at android.os.Handler.sendMessageAtTime(Handler.java:631)
07-20 09:47:13.026 32255-689/net.openmob.mobileimsdk.android.demo W/zygote:     at android.os.Handler.sendMessageDelayed(Handler.java:601)
07-20 09:47:13.026 32255-689/net.openmob.mobileimsdk.android.demo W/zygote:     at android.os.Handler.sendMessage(Handler.java:538)
07-20 09:47:13.026 32255-689/net.openmob.mobileimsdk.android.demo W/zygote:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever.p2pListeningImpl(LocalUDPDataReciever.java:113)
07-20 09:47:13.026 32255-689/net.openmob.mobileimsdk.android.demo W/zygote:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever.access$100(LocalUDPDataReciever.java:36)
07-20 09:47:13.027 32255-689/net.openmob.mobileimsdk.android.demo W/zygote:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever$1.run(LocalUDPDataReciever.java:85)
07-20 09:47:13.027 32255-689/net.openmob.mobileimsdk.android.demo W/zygote:     at java.lang.Thread.run(Thread.java:764)
07-20 09:47:13.028 32255-689/net.openmob.mobileimsdk.android.demo W/zygote: Contender stack:
07-20 09:47:13.028 32255-689/net.openmob.mobileimsdk.android.demo W/zygote:     at java.net.DatagramSocket.receive(DatagramSocket.java:-1)
07-20 09:47:13.028 32255-689/net.openmob.mobileimsdk.android.demo W/zygote:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever.p2pListeningImpl(LocalUDPDataReciever.java:110)
07-20 09:47:13.028 32255-689/net.openmob.mobileimsdk.android.demo W/zygote:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever.access$100(LocalUDPDataReciever.java:36)
07-20 09:47:13.028 32255-689/net.openmob.mobileimsdk.android.demo W/zygote:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever$1.run(LocalUDPDataReciever.java:85)
07-20 09:47:13.028 32255-689/net.openmob.mobileimsdk.android.demo W/zygote:     at java.lang.Thread.run(Thread.java:764)
07-20 09:47:13.045 32255-32255/net.openmob.mobileimsdk.android.demo D/LocalUDPDataReciever: 【IMCORE】收到服务端回过来的Keep Alive心跳响应包.
07-20 09:47:16.012 32255-32333/net.openmob.mobileimsdk.android.demo D/KeepAliveDaemon: 【IMCORE】心跳线程执行中...
07-20 09:47:16.069 32255-32333/net.openmob.mobileimsdk.android.demo D/LocalUDPSocketProvider: 【IMCORE】isLocalUDPSocketReady()==true,直接返回本地socket引用哦。
07-20 09:47:16.076 32255-395/net.openmob.mobileimsdk.android.demo D/LocalUDPSocketProvider: 【IMCORE】isLocalUDPSocketReady()==true,直接返回本地socket引用哦。
07-20 09:47:16.078 32255-860/net.openmob.mobileimsdk.android.demo W/zygote: Long monitor contention with owner Thread-12 (395) at void java.net.DatagramSocket.receive(java.net.DatagramPacket)(DatagramSocket.java:-1) waiters=11 in void java.net.DatagramSocket.receive(java.net.DatagramPacket) for 24.315s
07-20 09:47:16.079 32255-860/net.openmob.mobileimsdk.android.demo W/zygote: Current owner stack:
07-20 09:47:16.079 32255-860/net.openmob.mobileimsdk.android.demo W/zygote:     at android.os.MessageQueue.nativeWake(Native method)
07-20 09:47:16.079 32255-860/net.openmob.mobileimsdk.android.demo W/zygote:     at android.os.MessageQueue.enqueueMessage(MessageQueue.java:589)
07-20 09:47:16.080 32255-860/net.openmob.mobileimsdk.android.demo W/zygote:   - locked <0x0180179a> (a android.os.MessageQueue)
07-20 09:47:16.080 32255-860/net.openmob.mobileimsdk.android.demo W/zygote:     at android.os.Handler.enqueueMessage(Handler.java:662)
07-20 09:47:16.080 32255-860/net.openmob.mobileimsdk.android.demo W/zygote:     at android.os.Handler.sendMessageAtTime(Handler.java:631)
07-20 09:47:16.080 32255-860/net.openmob.mobileimsdk.android.demo W/zygote:     at android.os.Handler.sendMessageDelayed(Handler.java:601)
07-20 09:47:16.080 32255-860/net.openmob.mobileimsdk.android.demo W/zygote:     at android.os.Handler.sendMessage(Handler.java:538)
07-20 09:47:16.081 32255-860/net.openmob.mobileimsdk.android.demo W/zygote:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever.p2pListeningImpl(LocalUDPDataReciever.java:113)
07-20 09:47:16.081 32255-860/net.openmob.mobileimsdk.android.demo W/zygote:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever.access$100(LocalUDPDataReciever.java:36)
07-20 09:47:16.081 32255-860/net.openmob.mobileimsdk.android.demo W/zygote:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever$1.run(LocalUDPDataReciever.java:85)
07-20 09:47:16.081 32255-860/net.openmob.mobileimsdk.android.demo W/zygote:     at java.lang.Thread.run(Thread.java:764)
07-20 09:47:16.081 32255-860/net.openmob.mobileimsdk.android.demo W/zygote: Contender stack:
07-20 09:47:16.081 32255-860/net.openmob.mobileimsdk.android.demo W/zygote:     at java.net.DatagramSocket.receive(DatagramSocket.java:-1)
07-20 09:47:16.081 32255-860/net.openmob.mobileimsdk.android.demo W/zygote:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever.p2pListeningImpl(LocalUDPDataReciever.java:110)
07-20 09:47:16.081 32255-860/net.openmob.mobileimsdk.android.demo W/zygote:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever.access$100(LocalUDPDataReciever.java:36)
07-20 09:47:16.081 32255-860/net.openmob.mobileimsdk.android.demo W/zygote:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever$1.run(LocalUDPDataReciever.java:85)
07-20 09:47:16.082 32255-860/net.openmob.mobileimsdk.android.demo W/zygote:     at java.lang.Thread.run(Thread.java:764)
07-20 09:47:16.085 32255-32255/net.openmob.mobileimsdk.android.demo D/LocalUDPDataReciever: 【IMCORE】收到服务端回过来的Keep Alive心跳响应包.
07-20 09:47:16.936 32255-32332/net.openmob.mobileimsdk.android.demo D/QoS4SendDaemon: 【IMCORE】【QoS】=========== 消息发送质量保证线程运行中, 当前需要处理的列表长度为0...
07-20 09:47:19.073 32255-32339/net.openmob.mobileimsdk.android.demo D/KeepAliveDaemon: 【IMCORE】心跳线程执行中...
07-20 09:47:19.097 32255-32339/net.openmob.mobileimsdk.android.demo D/LocalUDPSocketProvider: 【IMCORE】isLocalUDPSocketReady()==true,直接返回本地socket引用哦。
07-20 09:47:19.148 32255-395/net.openmob.mobileimsdk.android.demo D/LocalUDPSocketProvider: 【IMCORE】isLocalUDPSocketReady()==true,直接返回本地socket引用哦。
后面都是重复的了
图片
3W8)G97]@49Y9%7SLQXV]NL.png
~4LB_CKP3SUJHJG{IEN`VNO.png
WPRP(B1IZ[_HXJ2X]5DR_Y2.png
既然能复现,你可以说说这是什么情况下出现的?另外,出现这种现状之后,能否自已恢复?(也就是后面是否还可以正常通信)
签名: 《新浪微博技术分享:微博实时直播答题的百万高并发架构实践》http://www.52im.net/thread-2022-1-1.html
引用:JackJiang 发表于 2018-07-20 10:14
既然能复现,你可以说说这是什么情况下出现的?另外,出现这种现状之后,能否自已恢复?(也就是后面是否还 ...

private void p2pListeningImpl() throws Exception
        {
                while (true)
                {
                        byte[] data = new byte[1024];
                        DatagramPacket packet = new DatagramPacket(data, data.length);
                        DatagramSocket localUDPSocket = LocalUDPSocketProvider.getInstance().getLocalUDPSocket();
                        if (localUDPSocket != null && !localUDPSocket.isClosed())
                        {
                                localUDPSocket.receive(packet);
                                Message m = Message.obtain();
                                m.obj = packet;
                                messageHandler.sendMessage(m);
                        }
                }
        }

                                messageHandler.sendMessage(m);的这里,不影响发送消息和登陆
引用:cha8511995 发表于 2018-07-20 10:27
private void p2pListeningImpl() throws Exception
        {
                while (true)

只要不影响就没事,因为网络操作是很耗电的事情,各种乱七八糟的手机以及系统被厂商定制后,对省电策略的定义都不一样,可能会能网络相关的操作做出各种限制。只要MobileIMSDK的算法能在网络被系统限制后自动恢复,就是算法运行的正常范畴。
签名: 《新浪微博技术分享:微博实时直播答题的百万高并发架构实践》http://www.52im.net/thread-2022-1-1.html
打赏楼主 ×
使用微信打赏! 使用支付宝打赏!

返回顶部