- 最新
- 投票最多
- 评论最多
I figured out the issue. I had added an exclusion for the dependency for UrlConnectionHttpClient
in the AWS dependencies use but it wasn't being honored by Gradle. The reason being that there was another internal library that we have that also brings in AWS dependencies. Gradle let the internal dependency override the explicit exclusion I had added. So when I added the exclusion in that library for the dependency that contains UrlConnectionHttpClient
it finally excluded it.
For the record we manually set the HttpClient but what happens with WebIdentityTokenFileCredentialsProvider
is it's looking at the classpath and if it finds more than one it throws the exception noted above.
Hello,
In regards to the error -
SdkClientException: Multiple HTTP implementations were found on the classpath
This usually means that you have more than one HTTP client in your classpath (ApacheHttpClient and UrlConnectionHttpClient for example), the SDK was not able to choose one by default. You need to explicitly set which http client you want to use in the client definition.
If you still have any Java SDK issues, please feel free to post them here -
References: [1] https://aws.amazon.com/blogs/developer/introducing-aws-common-runtime-http-client-in-the-aws-sdk-for-java-2-x/
相关内容
- AWS 官方已更新 3 年前
- AWS 官方已更新 2 年前