开发者社区> 问答> 正文

关于Jboot error - group lookup thread fail!:报错

@理工男海哥 你好,想跟你请教个问题:基于RPC 经常性的出现连接请求超时。
 

2018-05-17 18:25:30.355 [INFO ] serviceStatsLog - [motan-memoryStatistic] 218.72MB of 3616.00 MB (6.0%) used 
2018-05-17 18:25:31.952 [ERROR] error - group lookup thread fail!
com.ecwid.consul.transport.TransportException: java.net.SocketTimeoutException: Read timed out
    at com.ecwid.consul.transport.AbstractHttpTransport.executeRequest(AbstractHttpTransport.java:77)
    at com.ecwid.consul.transport.AbstractHttpTransport.makeGetRequest(AbstractHttpTransport.java:34)
    at com.ecwid.consul.v1.ConsulRawClient.makeGetRequest(ConsulRawClient.java:128)
    at com.ecwid.consul.v1.health.HealthConsulClient.getHealthServices(HealthConsulClient.java:99)
    at com.ecwid.consul.v1.health.HealthConsulClient.getHealthServices(HealthConsulClient.java:80)
    at com.ecwid.consul.v1.ConsulClient.getHealthServices(ConsulClient.java:440)
    at com.weibo.api.motan.registry.consul.client.ConsulEcwidClient.lookupHealthService(ConsulEcwidClient.java:50)
    at com.weibo.api.motan.registry.consul.ConsulRegistry.lookupConsulService(ConsulRegistry.java:258)
    at com.weibo.api.motan.registry.consul.ConsulRegistry.lookupServiceUpdate(ConsulRegistry.java:216)
    at com.weibo.api.motan.registry.consul.ConsulRegistry.access$100(ConsulRegistry.java:21)
    at com.weibo.api.motan.registry.consul.ConsulRegistry$ServiceLookupThread.run(ConsulRegistry.java:343)
Caused by: java.net.SocketTimeoutException: Read timed out
    at java.net.SocketInputStream.socketRead0(Native Method)
    at java.net.SocketInputStream.socketRead(Unknown Source)
    at java.net.SocketInputStream.read(Unknown Source)
    at java.net.SocketInputStream.read(Unknown Source)
    at org.apache.http.impl.io.SessionInputBufferImpl.streamRead(SessionInputBufferImpl.java:137)
    at org.apache.http.impl.io.SessionInputBufferImpl.fillBuffer(SessionInputBufferImpl.java:153)
    at org.apache.http.impl.io.SessionInputBufferImpl.readLine(SessionInputBufferImpl.java:282)
    at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:138)
    at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:56)
    at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:259)
    at org.apache.http.impl.DefaultBHttpClientConnection.receiveResponseHeader(DefaultBHttpClientConnection.java:163)
    at org.apache.http.impl.conn.CPoolProxy.receiveResponseHeader(CPoolProxy.java:165)
    at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:273)
    at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:125)
    at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:272)
    at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:185)
    at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:89)
    at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:111)
    at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185)
    at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:72)
    at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:221)
    at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:165)
    at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:140)
    at com.ecwid.consul.transport.AbstractHttpTransport.executeRequest(AbstractHttpTransport.java:61)
    ... 10 common frames omitted

展开
收起
kun坤 2020-06-14 14:36:32 901 0
1 条回答
写回答
取消 提交回答
  • 网络原因出现的可能性太多了,不好说具体什么原因。可以换个环境测试下,或者把motan换成dubbo试试。######

    得勒,谢海哥!

    2020-06-14 14:36:36
    赞同 展开评论 打赏
问答地址:
问答排行榜
最热
最新

相关电子书

更多
In-Flux Limiting for a Multi-Tenant Logging Service 立即下载
How to Build a Successful Data 立即下载
Using Hadoop to build a Data Quality Service for both real-time and batch data 立即下载