-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
quarkus-amazon-lambda-rest doesn't support Java 17 ? #39038
Comments
/cc @matejvasek (amazon-lambda), @patriot1burke (amazon-lambda) |
We should definitely adjust the default runtime but we need to find a working value. From what I can see, |
The descriptor might need some other changes but I have no experience with lambdas so can't really help. |
The file |
Using the last release of |
Describe the bug
I'm using Quarkus 3.7.4 with the
quarkus-amazon-lambda-rest
extension. The build generates the followingsam.jvm.yaml
file in thetarget
directory:The default runtime is, for some reason, Java 11. I'm modifying it to be Java 17 and I run the floowing command:
Then running my integration tests I get the following:
Expected behavior
I expect that the integration tests run successfully.
Actual behavior
The mention exception is raised.
How to Reproduce?
Don't have a reproducer
Output of
uname -a
orver
Linux nicolas-XPS-13-9360 6.5.0-21-generic #21~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb 9 13:32:52 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
Output of
java -version
java version "17.0.6" 2023-01-17 LTS Java(TM) SE Runtime Environment (build 17.0.6+9-LTS-190) Java HotSpot(TM) 64-Bit Server VM (build 17.0.6+9-LTS-190, mixed mode, sharing)
Quarkus version or git rev
3.7.4
Build tool (ie. output of
mvnw --version
orgradlew --version
)Maven home: /opt/apache-maven-3.9.4 Java version: 17.0.6, vendor: Oracle Corporation, runtime: /usr/lib/jvm/jdk-17 Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "6.5.0-21-generic", arch: "amd64", family: "unix"
Additional information
The following command:
raises exactly the same exception.
The text was updated successfully, but these errors were encountered: