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

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

liubao68 commented on a change in pull request #486: [SCB-165] Service registry 
not given proper instances
URL: 
https://github.com/apache/incubator-servicecomb-java-chassis/pull/486#discussion_r159877061
 
 

 ##########
 File path: 
service-registry/src/main/java/io/servicecomb/serviceregistry/client/http/ServiceRegistryClientImpl.java
 ##########
 @@ -111,7 +111,8 @@ private void retry(RequestContext requestContext, 
Handler<RestResponse> response
               holder.value =
                   JsonUtils.readValue(bodyBuffer.getBytes(), cls);
             } catch (Exception e) {
-              LOGGER.warn(bodyBuffer.toString());
+              LOGGER.warn("read value failed and response message is {}",
 
 Review comment:
   This is exception is always Json Parse exceptions and no need to print out.

----------------------------------------------------------------
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:
us...@infra.apache.org


> Service registry not given proper instances 
> --------------------------------------------
>
>                 Key: SCB-165
>                 URL: https://issues.apache.org/jira/browse/SCB-165
>             Project: Apache ServiceComb
>          Issue Type: Bug
>          Components: Java-Chassis
>            Reporter: liubao
>
> 1. when calling DynamicSchemaLoader at start up, and when the dependent 
> service is not registered when making calls, service center will not notify 
> client when service is registered.
> 2. when autodiscovery is enabled and service center is not started, 
> microservice will start fail.
> 3. when retrying in service center , if one instance failed, and when a lots 
> of calls to service center is made, next fallback address may have many 
> choose again to the failed instance. If this takes too long, will cause 
> instance idle and unregistered by service center.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to