connectSocket(): 123.56.72.122error: Connection timed out

问题描述

登录失败，且失败日志如下：03-23 10:45:32.744: D/LoginActivity(617): EMClient.getInstance().login03-23 10:45:32.745: D/ONE SDK(617): [2016/3/23 10:45:32:745]: emchat manager login in process:61703-23 10:45:32.752: D/ONE SDK(617): [2016/3/23 10:45:32:752]: EMSessionManager::login(): 1331131390803-23 10:45:32.752: I/hyphenate_jni(617): httprequest perform: http://112.126.66.111/easemob/ ... n%3D103-23 10:45:32.756: D/ONE SDK(617): [2016/3/23 10:45:32:752]: getDnsListFromServer()03-23 10:45:32.761: D/ONE SDK(617): [2016/3/23 10:45:32:752]: buildUrl(): http://112.126.66.111/easemob/ ... n%3D103-23 10:45:32.788: D/EMARHttpAPI(617): httpExecute code: 20003-23 10:45:32.790: I/hyphenate_jni(617): httprequest perform: http://182.92.228.160/easemob- ... token03-23 10:45:32.793: D/ONE SDK(617): [2016/3/23 10:45:32:788]: 1 time retry03-23 10:45:32.793: D/ONE SDK(617): [2016/3/23 10:45:32:788]: DNS List size: 88603-23 10:45:32.794: D/ONE SDK(617): [2016/3/23 10:45:32:788]: EMSessionManager::parseDnsServer: {"file_version":"1","resolver":{"hosts":[{"port":"80","domain":"rs.easemob.com","ip":"112.126.66.111"},{"port":"80","domain":"rs.easemob.com","ip":"182.92.174.78"}]},"rest":{"hosts":[{"protocol":"https","port":"443","domain":"a1.easemob.com"},{"protocol":"http","port":"80","domain":"a1.easemob.com","ip":"182.92.228.160"},{"protocol":"http","port":"80","domain":"a1.easemob.com","ip":"182.92.73.182"}]},"valid_before":"1460660400","im":{"hosts":[{"port":"443","domain":"im1.easemob.com","ip":"182.92.20.34"},{"port":"443","domain":"im1.easemob.com","ip":"182.92.20.117"},{"port":"443","domain":"im1.easemob.com","ip":"182.92.23.59"},{"port":"443","domain":"im1.easemob.com","ip":"182.92.26.56"}]},"deploy_name":"easemob","msync-im":{"hosts":[{"port":"6717","domain":"msync-im1.easemob.com","ip":"123.56.72.122"},{"port":"6717","domain":"msync-im1.easemob.com","ip":"101.200.75.129"}]}}03-23 10:45:32.795: D/ONE SDK(617): [2016/3/23 10:45:32:789]: current time: 145870113278903-23 10:45:32.795: D/ONE SDK(617): [2016/3/23 10:45:32:789]: valid time: 146066040000003-23 10:45:32.795: D/ONE SDK(617): [2016/3/23 10:45:32:789]: saveConfigs()03-23 10:45:32.795: D/ONE SDK(617): [2016/3/23 10:45:32:789]: write to config file: {03-23 10:45:32.795: D/ONE SDK(617):     "dns_time":"1460660400000"03-23 10:45:32.795: D/ONE SDK(617): }03-23 10:45:32.796: D/ONE SDK(617): [2016/3/23 10:45:32:790]: ranomOffer03-23 10:45:32.796: D/ONE SDK(617): [2016/3/23 10:45:32:790]: imServer before random: 03-23 10:45:32.796: D/ONE SDK(617): [2016/3/23 10:45:32:790]: 123.56.72.12203-23 10:45:32.796: D/ONE SDK(617): [2016/3/23 10:45:32:790]: 101.200.75.12903-23 10:45:32.797: D/ONE SDK(617): [2016/3/23 10:45:32:790]: randomServers 03-23 10:45:32.797: D/ONE SDK(617): [2016/3/23 10:45:32:790]: randomServers 03-23 10:45:32.798: D/ONE SDK(617): [2016/3/23 10:45:32:790]: randomServers 03-23 10:45:32.798: D/ONE SDK(617): [2016/3/23 10:45:32:790]: imServer after random: 03-23 10:45:32.799: D/ONE SDK(617): [2016/3/23 10:45:32:790]: 123.56.72.12203-23 10:45:32.799: D/ONE SDK(617): [2016/3/23 10:45:32:790]: 101.200.75.12903-23 10:45:32.799: D/ONE SDK(617): [2016/3/23 10:45:32:790]: fetchToken()03-23 10:45:32.799: D/ONE SDK(617): [2016/3/23 10:45:32:790]: restBaseUrl()03-23 10:45:32.800: D/ONE SDK(617): [2016/3/23 10:45:32:790]: EMDNSManager::getCurrentHost: type: 203-23 10:45:32.800: D/ONE SDK(617): [2016/3/23 10:45:32:790]: EMSessionManager::checkDNS()03-23 10:45:32.801: D/ONE SDK(617): [2016/3/23 10:45:32:790]: EMDNSManager::getHost: type: 203-23 10:45:32.801: D/ONE SDK(617): [2016/3/23 10:45:32:790]: current host: domain: 182.92.228.160 port: 8003-23 10:45:32.801: D/ONE SDK(617): [2016/3/23 10:45:32:790]: fetchTokenForUser()http://182.92.228.160/easemob-demo/chatdemoui/token03-23 10:45:32.836: D/EMARHttpAPI(617): httpExecute code: 20003-23 10:45:32.838: D/ONE SDK(617): [2016/3/23 10:45:32:837]: [retrieve token time] 0: 0: 4603-23 10:45:32.838: D/ONE SDK(617): [2016/3/23 10:45:32:837]: fetchToken success 03-23 10:45:32.838: D/ONE SDK(617): [2016/3/23 10:45:32:837]: saveToken(): user: 13311313908 time: 145870113283703-23 10:45:32.883: D/ONE SDK(617): [2016/3/23 10:45:32:883]: savetoken() result: 103-23 10:45:32.883: D/ONE SDK(617): [2016/3/23 10:45:32:883]: token is valid:   time: 145870113283703-23 10:45:32.884: D/ONE SDK(617): [2016/3/23 10:45:32:883]: EMDNSManager::getCurrentHost: type: 103-23 10:45:32.885: D/ONE SDK(617): [2016/3/23 10:45:32:883]: EMSessionManager::checkDNS()03-23 10:45:32.885: D/ONE SDK(617): [2016/3/23 10:45:32:883]: EMDNSManager::getHost: type: 103-23 10:45:32.885: D/ONE SDK(617): [2016/3/23 10:45:32:883]: current host: domain: 123.56.72.122 port: 671703-23 10:45:32.885: D/ONE SDK(617): [2016/3/23 10:45:32:883]: setServer: 123.56.72.12203-23 10:45:32.885: D/ONE SDK(617): [2016/3/23 10:45:32:883]: Calling connect...03-23 10:45:32.885: D/ONE SDK(617): [2016/3/23 10:45:32:883]: doConnect()03-23 10:45:32.885: D/ONE SDK(617): [2016/3/23 10:45:32:883]: current connectState: 003-23 10:45:32.889: D/ONE SDK(617): [2016/3/23 10:45:32:884]: log: level: 0, area: 1, ChatClient::connect() 03-23 10:45:32.893: D/ONE SDK(617): [2016/3/23 10:45:32:884]: log: level: 0, area: 2, getSocket(): 3703-23 10:45:32.895: D/ONE SDK(617): [2016/3/23 10:45:32:884]: log: level: 1, area: 2, connectSocket(): start to connecting...03-23 10:46:12.924: D/ONE SDK(617): [2016/3/23 10:46:12:922]: log: level: 2, area: 2, connectSocket(): 123.56.72.122error: Connection timed out03-23 10:46:12.931: D/LoginActivity(617): login: onError: 30303-23 10:46:12.936: D/ONE SDK(617): [2016/3/23 10:46:12:922]: log: level: 1, area: 2, closeSocket() 03-23 10:46:12.941: D/ONE SDK(617): [2016/3/23 10:46:12:923]: log: level: 1, area: 2, connectSocket(): connect finished03-23 10:46:12.941: D/ONE SDK(617): [2016/3/23 10:46:12:923]: log: level: 2, area: 2, connect(): connect timeout03-23 10:46:12.942: D/ONE SDK(617): [2016/3/23 10:46:12:923]: log: level: 1, area: 2, cleanup() 03-23 10:46:12.943: D/ONE SDK(617): [2016/3/23 10:46:12:923]: log: level: 2, area: 1, handleDisconnect:603-23 10:46:12.943: D/ONE SDK(617): [2016/3/23 10:46:12:923]: EMSessionManager::onDisConnect(): 603-23 10:46:12.949: D/ONE SDK(617): [2016/3/23 10:46:12:923]: stopReceive()03-23 10:46:12.950: D/ONE SDK(617): [2016/3/23 10:46:12:923]: log: level: 0, area: 1, ChatClient::disconnect()03-23 10:46:12.950: D/ONE SDK(617): [2016/3/23 10:46:12:923]: log: level: 1, area: 2, cleanup() 03-23 10:46:12.951: D/ONE SDK(617): [2016/3/23 10:46:12:925]: log: level: 2, area: 1, handleDisconnect:1403-23 10:46:12.952: D/ONE SDK(617): [2016/3/23 10:46:12:925]: network issue, just reconnect after random time03-23 10:46:12.952: D/ONE SDK(617): [2016/3/23 10:46:12:925]: Calling connect result: 003-23 10:46:12.953: D/ONE SDK(617): [2016/3/23 10:46:12:925]: login failed: 30303-23 10:46:12.961: D/ONE SDK(617): [2016/3/23 10:46:12:925]: [im login time] 0:40: 4203-23 10:46:12.962: D/ONE SDK(617): [2016/3/23 10:46:12:925]: login return: 30303-23 10:46:12.963: D/ONE SDK(617): [2016/3/23 10:46:12:926]: do stop service03-23 10:46:12.970: D/ONE SDK(617): [2016/3/23 10:46:12:954]: onDestroy 请问这是什么原因？

解决方案

换网络操作看看

时间： 2024-10-03 02:46:20

connectSocket(): 123.56.72.122error: Connection timed out的相关文章

jvm-rmi 链接超时 Connection timed out: connect

问题描述 rmi 链接超时 Connection timed out: connect 说要设置 jvm参数 -Dsun.rmi.transport.proxy.connectTimeout=6000 -Dsun.rmi.transport.tcp.responseTimeout=6000 请问这个参数在哪里设置? 解决方案 Connection timed out: connectError:Connection timed out:connect.Error:Connection timed

连接超时-Connection timed out:

问题描述 Connection timed out: java.net.ConnectException: Connection timed out: connect java.net.PlainSocketImpl.socketConnect(Native Method) java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351) java.net.PlainSocketImpl.connectToAddress(PlainSock

【Oracle】 inbound connection timed out (ORA-3136)

早上突然接到监控报警WARNING: inbound connection timed out (ORA-3136). ora-3136 连接超时在大部分情况下是可以忽略的,这个错误一般是由于客户端由于没有使用正确登录的密码,连接超时导致. 比如下面的例子: oracle@rac1:/home/oracle>sqlplus yang/yan@yangdbstd  SQL*Plus: Release 11.2.0.1.0 Production on Wed Sep 21 10:47:35 2011

db2-sqoop连接DB2import 时报错，Connection timed out 求大神解答

问题描述 sqoop连接DB2import 时报错,Connection timed out 求大神解答 sqoop连接DB2导入数据至HDFS时,报错,显示连接超时. 用list-table命令连接没有问题?,结果正确: 测试过DB2远程连接,没有问题,telnet 测试端口也没有问题: DB2版本v9.7,用的安装包里面的JDBC插件. 以下是错误信息. [biadmin@Hadoop01 sqoop]$ ./bin/sqoop import --connect jdbc:db2://9.1

抓取网站数据 报Connection timed out

问题描述 做了一个抓取网站的功能,用的是httpclient.在自己的电脑上运行,可以抓取到.但是把工程发布到服务器上,就会报I/O exception (java.net.ConnectException) caught when processing request: Connection timed out请问,是什么原因啊? 解决方案 目测判断:你的服务器与目标网站没有成功连接.排查方法:1.检查目标地址,确保服务器上,你访问的url与本地一致(如果是通过配置文件配置,请检查配置文件):

java.lang.RuntimeException: java.net.ConnectException: Connection timed out: con

问题描述 报这个错误java.lang.RuntimeException:java.net.ConnectException:Connectiontimedout:connectatorg.jasig.cas.client.util.CommonUtils.getResponseFromServer(CommonUtils.java:346)atorg.jasig.cas.client.util.CommonUtils.getResponseFromServer(CommonUtils.java

Connection timed out:could be due to invalid address

问题描述 报错:Connectiontimedout:couldbeduetoinvalidaddress配置:tomcat5.informix现象:登录时IE一直在转,就是登陆不进去发生原因不详,但的确是在程序正常运行一天之后发生的,数据库连接配置一直都没有改然后再无其他的报错信息在log日志就看到这么多请教各位高手谁能解开本人的困惑,感激不尽. 解决方案 解决方案二:是不是服务器端口closedwait了

CloudFlare Support - Error 522: Connection timed out 错误522：连接超时

522错误意味着我们无法在所有到达原点Web服务器.  这方面有几个主要原因: 原始服务器太超载回应. 源Web服务器具有挡住了我们的请求的防火墙,或者数据包被主机的网络内下降. 源Web服务器脱机,或与我们不正确的DNS设置为它的IP地址设置(即离我们的要求是送错了地方). 还有我们和原始Web服务器之间的网络路由问题. 起源服务器保持连接禁用. 在所有这些情况下,这是值得检查原点Web服务器是活动的,才去进一步这里接受HTTP请求,同时也与我们在您的帐户的DNS设置正确. 原始服务器太超载回

android easeUI 3.0 登录失败 303 Unknown server error.换回2.0就可以登录成功，请问啥错啊

问题描述 解决方案 测试可以登陆了,你再试试解决方案二:我也试过了,同样的问题,3.0登录失败,2.0登录成功解决方案三:@Ice Butterfly 现在还有这样的情况?登陆失败? 把具体报错信息贴出来看看解决方案四:登录时日志:03-23 10:45:32.744: D/LoginActivity(617): EMClient.getInstance().login03-23 10:45:32.745: D/ONE SDK(617): [2016/3/23 10:45:32:745]: em