GetBlobStoreContext failing after updating the aws-sdk
melwinlobo21 opened this issue · 3 comments
Describe the bug
We have updated aws-sdk-java from 1.12.464 to 1.12.641
After updating AmazonWebServiceConfiguration.getBlobStoreContext
is failing with following error:
1) [Guice/ErrorInCustomProvider]: NoSuchMethodError: 'void ConstructorConstructor.<init>(Map)'
at GsonModule.provideGson(GsonModule.java:99)
\_ installed by: AWSS3HttpApiModule -> GsonModule
at GsonWrapper.<init>(GsonWrapper.java:38)
\_ for 1st parameter
at GsonWrapper.class(GsonWrapper.java:32)
while locating GsonWrapper
while locating Json
The complete trace is quite long. I have included it in this file:
error_logs.txt
Expected Behavior
ContextBuilder.newBuilder(ObjectStoreServiceProviders.PROVIDER_AWS.toString())
.credentials(this.getAccessKeyId(), this.getSecretAccessKey())
.buildView(BlobStoreContext.class)
To return the BlobStoreContext
Current Behavior
Described above.
Reproduction Steps
Upgrade to 1.12.641
Possible Solution
No response
Additional Information/Context
Dependencies Used:
<dependency>
<groupId>com.amazonaws</groupId>
<artifactId>aws-java-sdk-bom</artifactId>
<version>1.12.641</version>
<type>pom</type>
<scope>import</scope>
</dependency>
<dependency>
<groupId>com.amazonaws</groupId>
<artifactId>aws-java-sdk-core</artifactId>
</dependency>
<dependency>
<groupId>com.amazonaws</groupId>
<artifactId>aws-java-sdk-s3</artifactId>
<dependency>
AWS Java SDK version used
1.12.641
JDK version used
17
Operating System and version
MacOS
@melwinlobo21 What's AmazonWebServiceConfiguration.getBlobStoreContext
, is it your code?
Also, I see you're using Guice/Gson, which are Google libraries. If the error is being thrown by those libs you'll need to reach out to their maintainers.
Hey @debora-ito ,
Thanks for the response. The issue was due to the JClouds library not being compatible with Gson 2.9 (https://issues.apache.org/jira/browse/JCLOUDS-1620)
This is not related to AWS SDK. Sorry for the trouble.
Regards,
Melwin Lobo
COMMENT VISIBILITY WARNING
Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.