[ 
https://issues.apache.org/jira/browse/SCB-705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16527477#comment-16527477
 ] 

ASF GitHub Bot commented on SCB-705:
------------------------------------

coveralls edited a comment on issue #785: [SCB-705] consumer don't cache 
ReferenceConfig of an unregistered provider
URL: 
https://github.com/apache/incubator-servicecomb-java-chassis/pull/785#issuecomment-401231253
 
 
   
   [![Coverage 
Status](https://coveralls.io/builds/17755813/badge)](https://coveralls.io/builds/17755813)
   
   Coverage increased (+0.01%) to 87.147% when pulling 
**53a6ad63d3c1fb19d29f3a6af1c6dd686f948f81 on 
yhs0092:fix_consumer_microservice_discovery_ability** into 
**bb4b6986f21dfa35d8ab83868e9cb7d60ecfe3e0 on apache:master**.
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


> When consumer invoke an unregistered provider, it will never find this 
> provider even the provider is registered later
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: SCB-705
>                 URL: https://issues.apache.org/jira/browse/SCB-705
>             Project: Apache ServiceComb
>          Issue Type: Bug
>          Components: Java-Chassis
>            Reporter: YaoHaishi
>            Assignee: YaoHaishi
>            Priority: Major
>
> Before consumer invoke provider, it will create a ReferenceConfig for this 
> provider. But when the provider is not registered, it will get a wrong 
> ReferenceConfig and cache it, so it will never query the service-center again 
> to get the provider microservice information, and an Exception is always 
> thrown to say that the provider cannot be found.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to