Issues with native compilation using S3 sdk #2086
Comments
cmoine
added
guidance
|
After 3 days of investigation, I finally found the problem: S3 SDK use execution interceptors. The execution interceptor is loaded dynamically, and thus requires to add this in the {"pattern":"\\Qsoftware/amazon/awssdk/services/s3/execution.interceptors\\E"}After that modification, the classes listed in that file required to be accessible reflectively in "reflect-config.json" file: {
"name":"software.amazon.awssdk.services.s3.internal.handlers.AddContentMd5HeaderInterceptor",
"methods":[{"name":"<init>","parameterTypes":[] }]
},
{
"name":"software.amazon.awssdk.services.s3.internal.handlers.AsyncChecksumValidationInterceptor",
"methods":[{"name":"<init>","parameterTypes":[] }]
},
{
"name":"software.amazon.awssdk.services.s3.internal.handlers.CreateBucketInterceptor",
"methods":[{"name":"<init>","parameterTypes":[] }]
},
{
"name":"software.amazon.awssdk.services.s3.internal.handlers.CreateMultipartUploadRequestInterceptor",
"methods":[{"name":"<init>","parameterTypes":[] }]
},
{
"name":"software.amazon.awssdk.services.s3.internal.handlers.DecodeUrlEncodedResponseInterceptor",
"methods":[{"name":"<init>","parameterTypes":[] }]
},
{
"name":"software.amazon.awssdk.services.s3.internal.handlers.DisableDoubleUrlEncodingInterceptor",
"methods":[{"name":"<init>","parameterTypes":[] }]
},
{
"name":"software.amazon.awssdk.services.s3.internal.handlers.EnableChunkedEncodingInterceptor",
"methods":[{"name":"<init>","parameterTypes":[] }]
},
{
"name":"software.amazon.awssdk.services.s3.internal.handlers.EnableTrailingChecksumInterceptor",
"methods":[{"name":"<init>","parameterTypes":[] }]
},
{
"name":"software.amazon.awssdk.services.s3.internal.handlers.EndpointAddressInterceptor",
"methods":[{"name":"<init>","parameterTypes":[] }]
},
{
"name":"software.amazon.awssdk.services.s3.internal.handlers.ExceptionTranslationInterceptor",
"methods":[{"name":"<init>","parameterTypes":[] }]
},
{
"name":"software.amazon.awssdk.services.s3.internal.handlers.GetBucketPolicyInterceptor",
"methods":[{"name":"<init>","parameterTypes":[] }]
},
{
"name":"software.amazon.awssdk.services.s3.internal.handlers.GetObjectInterceptor",
"methods":[{"name":"<init>","parameterTypes":[] }]
},
{
"name":"software.amazon.awssdk.services.s3.internal.handlers.PutObjectInterceptor",
"methods":[{"name":"<init>","parameterTypes":[] }]
},
{
"name":"software.amazon.awssdk.services.s3.internal.handlers.SyncChecksumValidationInterceptor",
"methods":[{"name":"<init>","parameterTypes":[] }]
}If this can helps other people, I'll be glad about that! As a conclusion, I have been punished for not using the native agent as described here: |
Removing CW integration test that fails and is no longer relevant
|
Just adding a comment here for anyone who has also fallen down this rabbit-hole. The |
This ticket is a subset of #1852 (Make SDK easily compileable to GraalVM native image)
Describe the issue
The AWS S3 Client has an awkward behavior with some characters in the URL (character ' ', '@' for instance) with native compilation using GraalVM
Steps to Reproduce
Use the following snippet:
Current Behavior
The second invocation raises this exception:
Our investigation so far regarding this issue:
Your Environment
v2.13.47
OpenJDK 64-Bit Server VM GraalVM 20.1.1-dev (build 25.252-b09-jvmci-20.1-b02, mixed mode)
Linux 64bits
The text was updated successfully, but these errors were encountered: