We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
大致原因是在CseUriTemplateHandler中的createUri方法会调用new URI方法创建一个url对象,而cse的url中appId:ServiceName会被解析为port,导致URI内部抛出URISyntaxException异常,进入异常捕获的逻辑
在高并发场景下,这里成为了性能瓶颈,是否可以考虑新增一种appId.ServiceName的形式呢?
The text was updated successfully, but these errors were encountered:
你描述的问题和并发有关系吗?能够提供一下重现方法?
Sorry, something went wrong.
可以看下https://github.com/apache/servicecomb-java-chassis/pull/4438, 是不是这个修复已经同时解决了你的问题?
链接丢失,这个场景是使用spring的RestTemplate必走的逻辑,创建对应的URI时,会走到URISyntaxException处理逻辑,实际不影响功能,只是在一些高性能要求下,可能会耗时比较多
No branches or pull requests
大致原因是在CseUriTemplateHandler中的createUri方法会调用new URI方法创建一个url对象,而cse的url中appId:ServiceName会被解析为port,导致URI内部抛出URISyntaxException异常,进入异常捕获的逻辑
在高并发场景下,这里成为了性能瓶颈,是否可以考虑新增一种appId.ServiceName的形式呢?
The text was updated successfully, but these errors were encountered: