You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@servicecomb.apache.org by GitBox <gi...@apache.org> on 2019/05/22 04:00:13 UTC

[GitHub] [servicecomb-java-chassis] yhs0092 commented on issue #1214: Customer无法获取Provider的服务地址

yhs0092 commented on issue #1214: Customer无法获取Provider的服务地址
URL: https://github.com/apache/servicecomb-java-chassis/issues/1214#issuecomment-494643243
 
 
   Please follow the check steps below:
   1. check the log of consumer, whether there is content like `find instances[{}] from service center success. service={}/{}/{}`. If yes, then go to step 2, otherwise the provider service instance may fail to register into service center, in which case you need to check the boot up process of provider service.
   2. check whether there is content like `not deployed transport {}, ignore {}.` in the log of consumer. If such log content appears, there are two possible causes. The first one is the transport components are not loaded, the second one is the transport components are loaded, but not added into `org.apache.servicecomb.core.transport.TransportManager`. It's easy to check the cause by looking up the log printed in `org.apache.servicecomb.core.transport.TransportManager#chooseOneTransport`. If in this method a transport component is chosen for the corresponding transport way, then it's quite certain that the transport component is loaded but not added into `TransportManager`. Such problem (not added to `TransportManager`) is usually caused by the repeatedly loading of Spring `ApplicationContext`, in which case you need to check the relative code and configuration : )

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services