servicecomb rpc 调用超时问题
错误日志如下:
org.apache.servicecomb.swagger.invocation.exception.InvocationException: InvocationException: code=490;msg=CommonExceptionData [message=Unexpected consumer error, please check logs for details]
60cac2cafff29e45e1f86e0b at org.apache.servicecomb.swagger.invocation.exception.ExceptionFactory.doCreate(ExceptionFactory.java:81)
60cac2cafff29e45e1f86e0b at org.apache.servicecomb.swagger.invocation.exception.ExceptionFactory.convertException(ExceptionFactory.java:124)
60cac2cafff29e45e1f86e0b at org.apache.servicecomb.swagger.invocation.exception.ExceptionFactory.convertConsumerException(ExceptionFactory.java:85)
60cac2cafff29e45e1f86e0b at org.apache.servicecomb.swagger.invocation.Response.createConsumerFail(Response.java:178)
60cac2cafff29e45e1f86e0b at org.apache.servicecomb.swagger.invocation.Response.createFail(Response.java:171)
60cac2cafff29e45e1f86e0b at org.apache.servicecomb.swagger.invocation.AsyncResponse.fail(AsyncResponse.java:42)
60cac2cafff29e45e1f86e0b at org.apache.servicecomb.transport.rest.client.http.RestClientInvocation.fail(RestClientInvocation.java:294)
60cac2cafff29e45e1f86e0b at org.apache.servicecomb.transport.rest.client.http.RestClientInvocation.lambda$new
0
(
R
e
s
t
C
l
i
e
n
t
I
n
v
o
c
a
t
i
o
n
.
j
a
v
a
:
86
)
60
c
a
c
2
c
a
f
f
f
29
e
45
e
1
f
86
e
0
b
a
t
o
r
g
.
a
p
a
c
h
e
.
s
e
r
v
i
c
e
c
o
m
b
.
t
r
a
n
s
p
o
r
t
.
r
e
s
t
.
c
l
i
e
n
t
.
h
t
t
p
.
R
e
s
t
C
l
i
e
n
t
I
n
v
o
c
a
t
i
o
n
.
l
a
m
b
d
a
0(RestClientInvocation.java:86) 60cac2cafff29e45e1f86e0b at org.apache.servicecomb.transport.rest.client.http.RestClientInvocation.lambda
0(RestClientInvocation.java:86)60cac2cafff29e45e1f86e0batorg.apache.servicecomb.transport.rest.client.http.RestClientInvocation.lambdainvoke$1(RestClientInvocation.java:125)
60cac2cafff29e45e1f86e0b at io.vertx.core.http.impl.HttpClientRequestBase.handleException(HttpClientRequestBase.java:133)
60cac2cafff29e45e1f86e0b at io.vertx.core.http.impl.HttpClientRequestImpl.handleException(HttpClientRequestImpl.java:370)
解决方案:
1.服务消费端 设置端请求超时时间
servicecomb.rest.client.connection.idleTimeoutInSeconds
2.服务提供方 设置请求超时时间
servicecomb.rest.server.connection.idleTimeoutInSeconds