Lambda failed with Java compiled into machine code

hi, We have a few lambda(s) deployed with native Java (compiled Java code down to machine code with Graalvm). It has been working with no issue in the last 4 months.

Since yesterday, intermittently, the lambda fails to execute with the following error message: The current machine does not support all of the following CPU features that are required by the image: [CX8, CMOV, FXSR, MMX, SSE, SSE2, SSE3, SSSE3, SSE4_1, SSE4_2, POPCNT, LZCNT, AVX, AVX2, BMI1, BMI2, FMA].

I think there is a compatibility issue here and would like some advise of how to resolve it.

thanks in advance, KC

Themen

Serverlos Kalkulation

Tags

AWS Lambda

Sprache

English

gefragt vor 3 Monaten320 Aufrufe

1 Antwort

Neueste
Die meisten Stimmen
Die meisten Kommentare

Sind diese Antworten hilfreich? Stimmen Sie der richtigen Antwort zu, damit die Community von Ihrem Wissen profitieren kann.

-1

If this is happening with Graalvm Java 17, try Graalvm Java 21. Also, try switching the Java versions in the Lambda to match this.

AWS-Eric

beantwortet vor 3 Monaten

KC
vor 3 Monaten
I am not sure that helps. After a bit of digging, this error could mean the deployed image is built with newer version of CPU architecture (with new CPU instructions); and I believe the issue is the lambda is deployed with old CPU architecture which does not have these instruction support.

Ref: https://github.com/quarkusio/quarkus/wiki/Migration-Guide-3.2#native-compilation---work-around-missing-cpu-features

I recon' the fix is to apply "-march=compatibility" option, instruct Graalvm to compile image with backwards-compatibility

Relevanter Inhalt

Wie verwende ich AWS SAM, um eine von Lambda unterstützte, benutzerdefinierte Ressource in Java für CloudFormation zu erstellen?
AWS OFFICIALAktualisiert vor einem Jahr
Wie behebe ich den Fehler „Bucket cannot have ACLs set with ObjectOwnership's BucketOwnerEnforced setting“ in CloudFormation?
AWS OFFICIALAktualisiert vor einem Jahr
Wie behebe ich die Fehler „ClassNotFoundException“ und „NoSuchMethodError“ einer Java-Lambda-Funktion?
AWS OFFICIALAktualisiert vor 2 Jahren
Wie kann ich die Latenz bei der Initialisierung und Aufrufdauer meiner Java-Lambda-Funktion verringern?
AWS OFFICIALAktualisiert vor 3 Jahren