时间戳

首页 > 解决方案 > api 无法将跟踪发送到 docker 容器中的 aws-xray 守护进程

java - api 无法将跟踪发送到 docker 容器中的 aws-xray 守护进程

问题描述

我有两个用于休息 API 和 X 射线守护程序的 docker 容器启动并运行。在我的本地，API 成功地将跟踪发送到 X 射线守护程序。但无法在docker中实现。

我遵循了这些步骤。

每当我试图访问我的 API 时，我都会遇到这样的异常

2020-06-03 08:08:33.799  INFO 1 --- [pool-1-thread-1] c.a.x.s.sampling.pollers.RulePoller      : Polling sampling rules.2020-06-03 08:08:34.413 ERROR 1 --- [pool-1-thread-1] c.a.x.s.sampling.pollers.RulePoller      : Encountered error polling GetSamplingRules:

com.amazonaws.SdkClientException：无法执行 HTTP 请求：连接到 0.0.0.0:2000 [/0.0.0.0] 失败：com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleRetryableException（AmazonHttpClient.java:第1207章~[aws-java-sdk-core-1.11.787.jar!/:na]在com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeHelper（AmazonHttpClient.java:1153）~[aws-java-sdk-core -1.11.787.jar!/:na] 在 com.amazonaws.http.AmazonHttpClient$RequestExecutor.doExecute(AmazonHttpClient.java:802) ~[aws-java-sdk-core-1.11.787.jar!/:na]在 com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeWithTimer(AmazonHttpClient.java:770) ~[aws-java-sdk-core-1.11.787.jar!/:na] 在 com.amazonaws.http.AmazonHttpClient$RequestExecutor。执行（AmazonHttpClient.java:744）~[aws-java-sdk-core-1.11.787.jar!/:na] 在 com.amazonaws.http.AmazonHttpClient$RequestExecutor.access$500(AmazonHttpClient.java:704) ~[aws-java-sdk-core-1.11.787.jar!/:na] 在 com.amazonaws .http.AmazonHttpClient$RequestExecutionBuilderImpl.execute(AmazonHttpClient.java:686) ~[aws-java-sdk-core-1.11.787.jar!/:na] at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java: 550）〜[aws-java-sdk-core-1.11.787.jar！/：na]在com.amazonaws.http.AmazonHttpClient.execute（AmazonHttpClient.java:530）〜[aws-java-sdk-core-1.11 .787.jar!/:na] 在 com.amazonaws.services.xray.AWSXRayClient.doInvoke(AWSXRayClient.java:1607) ~[aws-java-sdk-xray-1.11.787.jar!/:na] 在 com .amazonaws.services.xray.AWSXRayClient.invoke(AWSXRayClient.java:1574) ~[aws-java-sdk-xray-1.11.787.jar!/:na] 在 com.amazonaws.services.xray.AWSXRayClient。调用（AWSXRayClient.java:1563）~[aws-java-sdk-xray-1.11.787.jar!/:na] at com.amazonaws.services.xray.AWSXRayClient.executeGetSamplingRules（AWSXRayClient.java:800）~[aws -java-sdk-xray-1.11.787.jar!/:na] 在 com.amazonaws.services.xray.AWSXRayClient.getSamplingRules(AWSXRayClient.java:771) ~[aws-java-sdk-xray-1.11.787. jar!/:na] 在 com.amazonaws.xray.strategy.sampling.pollers.RulePoller.pollRule(RulePoller.java:65) ~[aws-xray-recorder-sdk-core-2.4.0.jar!/:na ] 在 com.amazonaws.xray.strategy.sampling.pollers.RulePoller.lambda$start$0(RulePoller.java:46) ~[aws-xray-recorder-sdk-core-2.4.0.jar!/:na] 在java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) ~[na:1.8.0_212] at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) ~[na:1.8.0_212 ] 在 java.util.concurrent。ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) ~[na:1.8.0_212] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) ~[na:1.8.0_212] at java .util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[na:1.8.0_212] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[na:1.8.0_212]在 java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_212] 引起：org.apache.http.conn.HttpHostConnectException: 连接到 0.0.0.0:2000 [/0.0.0.0] 失败: 在 org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:156) ~[httpclient-4.5.10.jar!/:4.5.10] 在 org.apache.http 的连接被拒绝（连接被拒绝） .impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:374) ~[httpclient-4.5.10.jar!/:4.5.10] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_212]在 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_212] 在 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_212] 在 java.lang .reflect.Method.invoke(Method.java:498) ~[na:1.8.0_212] at com.amazonaws.http.conn.ClientConnectionManagerFactory$Handler.invoke(ClientConnectionManagerFactory.java:76) ~[aws-java-sdk- core-1.11.787.jar!/:na] at com.amazonaws.http.conn.$Proxy64.connect(Unknown Source) ~[na:na] at org.apache.http.impl.execchain.MainClientExec.establishRoute( MainClientExec.java：393）〜[httpclient-4.5.10.jar！/：4.5.10] 10]在org.apache.http.impl.execchain.ProtocolExec.execute（ProtocolExec.java:186）〜[httpclient-4.5.10.jar !/:4.5.10] 在 org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185) ~[httpclient-4.5.10.jar!/:4.5.10] 在 org.apache.http .impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83) ~[httpclient-4.5.10.jar!/:4.5.10] at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java: 56) ~[httpclient-4.5.10.jar!/:4.5.10] 在 com.amazonaws.http.apache.client.impl.SdkHttpClient.execute(SdkHttpClient.java:72) ~[aws-java-sdk-core -1.11.787.jar!/:na] 在 com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeOneRequest(AmazonHttpClient.java:1330) ~[aws-java-sdk-core-1.11.787.jar!/:na]在 com.amazonaws。http.AmazonHttpClient$RequestExecutor.executeHelper(AmazonHttpClient.java:1145) ~[aws-java-sdk-core-1.11.787.jar!/:na] ... 省略了 21 个常见帧 原因：java.net.ConnectException：在 java.net.PlainSocketImpl.socketConnect(Native Method) ~[na:1.8.0_212] 在 java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) ~[na:1.8.0_212] 在java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:204) ~[na:1.8.0_212] 在 java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) ~[na:1.8.0_212] 在 java.net。 SocksSocketImpl.connect(SocksSocketImpl.java:392) ~[na:1.8.0_212] at java.net.Socket.connect(Socket.java:589) ~[na:1.8.0_212] at org.apache.http.conn。 socket.PlainConnectionSocketFactory。connectSocket(PlainConnectionSocketFactory.java:75) ~[httpclient-4.5.10.jar!/:4.5.10] at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:142) ~[httpclient-4.5 .10.jar!/:4.5.10] ...省略了37个常用框架

标签： javaspring-bootrestdockeraws-xray

解决方案

这可能是因为在 Docker 容器中运行的应用程序无法连接到在主机上本地运行的 X-Ray 守护程序。

您可能会发现此答案很有帮助。有一个简单的 Docker 平台示例，它在单独的容器中并排运行守护程序和应用程序。它使用 docker-compose 网络和AWS_XRAY_DAEMON_ADDRESS环境变量将应用程序容器连接到守护程序。

推荐阅读