-
Describe the bug: Unable to create Bean It's running on JDK 17 and we use an alpine 17 image as a base image. Expected Behavior Current Behavior Errors in Caused by: org.springframework.beans.BeanInstantiationException: Failed to instantiate [software.amazon.awssdk.services.s3.S3AsyncClient]: Factory method 's3AsyncClient' threw exception with message: Could not initialize class software.amazon.awssdk.crt.io.ClientBootstrap Possible Solution aws-crt-java version used Java version used Operating System and version
Based on this, I tried setting the classifier property to linux-x86_64-musl but this didn't affect the error at all. Could someone please suggest something I could be doing wrong ? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
Hi, thank you for creating the issue. You mentioned Alpine 17, but the If the issue persists, can you please share exact Docker image and JDK, along with a small, reproducible sample that you are using, to help debug this issue further? Whether Glibc or Musl is used depends on the installed JDK, not the OS. You can also try setting |
Beta Was this translation helpful? Give feedback.
-
Hi @waahm7 ! Thanks for the quick response. Can confirm that upgrading to an Alpine version >= 3.16 fixed the issue for us. |
Beta Was this translation helpful? Give feedback.
-
Hello! Reopening this discussion to make it searchable. |
Beta Was this translation helpful? Give feedback.
Hi, thank you for creating the issue. You mentioned Alpine 17, but the
os.detected.release.version
is3.14.3
. The binaries for Musl were compiled withAlpine 3.16
. Can you please try with an Alpine version >=3.16?If the issue persists, can you please share exact Docker image and JDK, along with a small, reproducible sample that you are using, to help debug this issue further? Whether Glibc or Musl is used depends on the installed JDK, not the OS. You can also try setting
aws.crt.libc
to glibc or musl if the CRT is not detecting it properly.