myVictor commented on issue #157: Zipkin web page have no tracing information 
at all
URL: 
https://github.com/apache/servicecomb-java-chassis/issues/157#issuecomment-466293287
 
 
   > 补充一下:
   > **1. webapp,calculator ,servicecenter,zipkin都在容器中运行。组网方式都是bridge. 
云主机地址是:192.168.100.101**
   > 
   > **2. 容器中的webapp和 calculator连接容器中的servicecenter(端口30100)是成功的。**
   > 
   > **3. webapp,calculator的容器启动参数分别为:**
   > 
   > ENTRYPOINT java -jar bmi-webapp-tracing.jar -Ptracing 
-Dservicecomb.tracing.collector.address=http://192.168.100.101:9411
   > 
   > ENTRYPOINT java -jar bmi-calculator-tracing.jar -Ptracing 
-Dcse.handler.chain.Provider.default=tracing-provider 
-Dservicecomb.tracing.collector.address=http://192.168.100.101:9411
   > 
   > **4. 访问报错信息:**
   > 
   > 2017/9/23 下午5:48:262017-09-23 09:48:26,378 [INFO] watching microservice 
6be7a0f09de911e7959a02efcacc0484 successfully, the chosen service center 
address is 192.168.100.101:30100 
io.servicecomb.serviceregistry.client.http.ServiceRegistryClientImpl.lambda$watch$6(ServiceRegistryClientImpl.java:520)
   > 2017/9/23 下午5:48:562017-09-23 09:48:56,262 [WARN] sc task interval changed 
from -1 to 30 
io.servicecomb.serviceregistry.task.ServiceCenterTaskMonitor.beginCycle(ServiceCenterTaskMonitor.java:38)
   > 2017/9/23 下午5:50:202017-09-23 09:50:20,301 [WARN] Dropped 1 spans due to 
ConnectException(Failed to connect to /127.0.0.1:9411) 
zipkin.reporter.AsyncReporter$BoundedAsyncReporter$1.onError(AsyncReporter.java:266)
   > 2017/9/23 下午5:50:20java.net.ConnectException: Failed to connect to 
/127.0.0.1:9411
   > 2017/9/23 下午5:50:20        at 
okhttp3.internal.connection.RealConnection.connectSocket(RealConnection.java:189)
 ~[okhttp-3.4.1.jar!/:?]
   > 2017/9/23 下午5:50:20        at 
okhttp3.internal.connection.RealConnection.buildConnection(RealConnection.java:173)
 ~[okhttp-3.4.1.jar!/:?]
   > 2017/9/23 下午5:50:20        at 
okhttp3.internal.connection.RealConnection.connect(RealConnection.java:114) 
~[okhttp-3.4.1.jar!/:?]
   > 2017/9/23 下午5:50:20        at 
okhttp3.internal.connection.StreamAllocation.findConnection(StreamAllocation.java:193)
 ~[okhttp-3.4.1.jar!/:?]
   > 2017/9/23 下午5:50:20        at 
okhttp3.internal.connection.StreamAllocation.findHealthyConnection(StreamAllocation.java:129)
 ~[okhttp-3.4.1.jar!/:?]
   > 2017/9/23 下午5:50:20        at 
okhttp3.internal.connection.StreamAllocation.newStream(StreamAllocation.java:98)
 ~[okhttp-3.4.1.jar!/:?]
   > 2017/9/23 下午5:50:20        at 
okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.java:42)
 ~[okhttp-3.4.1.jar!/:?]
   > 2017/9/23 下午5:50:20        at 
okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
 ~[okhttp-3.4.1.jar!/:?]
   > 2017/9/23 下午5:50:20        at 
okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67)
 ~[okhttp-3.4.1.jar!/:?]
   > 2017/9/23 下午5:50:20        at 
okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.java:109) 
~[okhttp-3.4.1.jar!/:?]
   > 2017/9/23 下午5:50:20        at 
okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
 ~[okhttp-3.4.1.jar!/:?]
   > 2017/9/23 下午5:50:20        at 
okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67)
 ~[okhttp-3.4.1.jar!/:?]
   > 2017/9/23 下午5:50:20        at 
okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.java:93) 
~[okhttp-3.4.1.jar!/:?]
   > 2017/9/23 下午5:50:20        at 
okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
 ~[okhttp-3.4.1.jar!/:?]
   > 2017/9/23 下午5:50:20        at 
okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.java:124)
 ~[okhttp-3.4.1.jar!/:?]
   > 2017/9/23 下午5:50:20        at 
okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
 ~[okhttp-3.4.1.jar!/:?]
   > 2017/9/23 下午5:50:20        at 
okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67)
 ~[okhttp-3.4.1.jar!/:?]
   > 2017/9/23 下午5:50:20        at 
okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:170) 
~[okhttp-3.4.1.jar!/:?]
   > 2017/9/23 下午5:50:20        at 
okhttp3.RealCall.access$100(RealCall.java:33) ~[okhttp-3.4.1.jar!/:?]
   > 2017/9/23 下午5:50:20        at 
okhttp3.RealCall$AsyncCall.execute(RealCall.java:120) [okhttp-3.4.1.jar!/:?]
   > 2017/9/23 下午5:50:20        at 
okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32) [okhttp-3.4.1.jar!/:?]
   > 2017/9/23 下午5:50:20        at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 
[?:1.8.0_144]
   > 2017/9/23 下午5:50:20        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 
[?:1.8.0_144]
   > 2017/9/23 下午5:50:20        at java.lang.Thread.run(Thread.java:748) 
[?:1.8.0_144]
   
   我也用这个例子自己实现了一个Edge 
Service(按照用户手册做的),问题是能查找服务信息,但是关系图无法生成出来,是什么原因?用的是URLMappedEdgeDispatcher

----------------------------------------------------------------
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


With regards,
Apache Git Services

Reply via email to