diwenzheng edited a comment on issue #2571:
URL:
https://github.com/apache/servicecomb-java-chassis/issues/2571#issuecomment-917598333
> > 更改了watch之后.好像还是有这个问题,
> > servicecomb:
> > service:
> > environment: development
> > application: XXX
> > name: mock-server
> > version: 1.1.0
> > registry:
> > address: ${REGISTRY_ADDRESS}
> > client:
> > timeout:
> > idle: 60
> > instance:
> > healthCheck:
> > interval: 60
> > times: 6
> > pull:
> > interval: 60
> > watch: true
> > empty:
> > pretection: true
> > autodiscovery: true
> > 2021-09-12 16:12:32.434 - [ERROR] - [registry-vert.x-eventloop-thread-1]
- [o.a.s.s.client.http.RestClientUtil] - [RestClientUtil.java:145] - GET
/v4/default/registry/instances?rev=5970674cffceb553d8e52ef4b944843af37c5743&appId=default&global=true&serviceName=SERVICECENTER&env=development&version=0.0.0.0%2B
fail, endpoint is 10.0.1.223:30100, message: Connection was closed
> > 2021-09-12 16:12:32.436 - [WARN] - [registry-vert.x-eventloop-thread-1]
- [o.a.s.s.c.h.ServiceRegistryClientImpl] -
[ServiceRegistryClientImpl.java:128] - invoke service [10.0.1.223:30100]
failed, retry address [10.0.1.224:30100].
> > 你的服务会有这些吗? 这让我困扰很久了.
>
> 你的链接timeout和pull的周期一致了，或许是这导致的问题：pull的时候尝试复用到了一个马上超时的链接，导致了Connection was
closed。
>
> 这只是从你配置中看到的可能的原因，进一步的debug确认应该可以证明这一点对不对。
感谢你的分享,之后我翻阅了资料,随后删除那些没有用的配置仅仅留着watch true
问题解决.至于原因我没有深究,但我觉得你的分析说的很有道理,灰常专业.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
