Bug: Powertools core utilities sam-graalvm example throw errors upon invocation #1934
Description
Expected Behaviour
The example for core utilities with GraalVM works without throwing an error.
Current Behaviour
When I run the existing core-utilities example with sam-graalvm, the function errors with a function runtime error. See debug log below.
Code snippet
sam build --use-container --build-image powertools-examples-core-sam-graalvmPossible Solution
It seems with the PR merge of #1927 this error occurs as the library has some changes with regards to the native libraries.
Steps to Reproduce
Run the examples/powertools-examples-core-utilities/sam-graalvm and notice the errors upon calling the rest api endpoint.
Powertools for AWS Lambda (Java) version
latest
AWS Lambda function runtime
provided.al2023
Debugging logs
2025/07/11/[$LATEST]4e7cedbfb877471dbc9d9c78fca8ccb0 2025-07-11T11:20:09.499000 INIT_START Runtime Version: provided:al2023.v100 Runtime Version ARN: arn:aws:lambda:eu-west-1::runtime:5e8de6bd50d624376ae13237e86c698fc23138eacd8186371c6930c98779d08f
2025/07/11/[$LATEST]4e7cedbfb877471dbc9d9c78fca8ccb0 2025-07-11T11:20:09.768000 Failed to load the native runtime interface client library libaws-lambda-jni.linux-x86_64.so. Exception: Specified file not in the JAR: libaws-lambda-jni.linux-x86_64.so
2025/07/11/[$LATEST]4e7cedbfb877471dbc9d9c78fca8ccb0 2025-07-11T11:20:09.769000 Failed to load the native runtime interface client library libaws-lambda-jni.linux-aarch_64.so. Exception: Specified file not in the JAR: libaws-lambda-jni.linux-aarch_64.so
2025/07/11/[$LATEST]4e7cedbfb877471dbc9d9c78fca8ccb0 2025-07-11T11:20:09.769000 Failed to load the native runtime interface client library libaws-lambda-jni.linux_musl-x86_64.so. Exception: Specified file not in the JAR: libaws-lambda-jni.linux_musl-x86_64.so
2025/07/11/[$LATEST]4e7cedbfb877471dbc9d9c78fca8ccb0 2025-07-11T11:20:09.769000 Failed to load the native runtime interface client library libaws-lambda-jni.linux_musl-aarch_64.so. Exception: Specified file not in the JAR: libaws-lambda-jni.linux_musl-aarch_64.so
2025/07/11/[$LATEST]4e7cedbfb877471dbc9d9c78fca8ccb0 2025-07-11T11:20:09.770000 INIT_REPORT Init Duration: 271.51 ms Phase: init Status: error Error Type: Runtime.ExitError
2025/07/11/[$LATEST]4e7cedbfb877471dbc9d9c78fca8ccb0 2025-07-11T11:20:10.436000 Failed to load the native runtime interface client library libaws-lambda-jni.linux-x86_64.so. Exception: Specified file not in the JAR: libaws-lambda-jni.linux-x86_64.so
2025/07/11/[$LATEST]4e7cedbfb877471dbc9d9c78fca8ccb0 2025-07-11T11:20:10.438000 Failed to load the native runtime interface client library libaws-lambda-jni.linux-aarch_64.so. Exception: Specified file not in the JAR: libaws-lambda-jni.linux-aarch_64.so
2025/07/11/[$LATEST]4e7cedbfb877471dbc9d9c78fca8ccb0 2025-07-11T11:20:10.438000 Failed to load the native runtime interface client library libaws-lambda-jni.linux_musl-x86_64.so. Exception: Specified file not in the JAR: libaws-lambda-jni.linux_musl-x86_64.so
2025/07/11/[$LATEST]4e7cedbfb877471dbc9d9c78fca8ccb0 2025-07-11T11:20:10.438000 Failed to load the native runtime interface client library libaws-lambda-jni.linux_musl-aarch_64.so. Exception: Specified file not in the JAR: libaws-lambda-jni.linux_musl-aarch_64.so
2025/07/11/[$LATEST]4e7cedbfb877471dbc9d9c78fca8ccb0 2025-07-11T11:20:10.439000 INIT_REPORT Init Duration: 649.88 ms Phase: invoke Status: error Error Type: Runtime.ExitError
2025/07/11/[$LATEST]4e7cedbfb877471dbc9d9c78fca8ccb0 2025-07-11T11:20:10.439000 START RequestId: cedd7a7d-ec13-477f-b768-0fbab0721524 Version: $LATEST
2025/07/11/[$LATEST]4e7cedbfb877471dbc9d9c78fca8ccb0 2025-07-11T11:20:10.456000 RequestId: cedd7a7d-ec13-477f-b768-0fbab0721524 Error: Runtime exited with error: exit status 255