-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Micronaut 1.3.5 and Netty 4.1.48.Final Graal Native Image Creation Failure #3341
Comments
@brianwyka do you have a test application for this? We have a basic test application for this and it works properly for both 1.3.x and master. |
I am also getting the same error while building graalvm native image
|
@msandy10 Your error seems related to using AWS SDK 2. We are soon going to be releasing GraalVM native image support for the AWS SDK 2. You can see snapshot docs here https://micronaut-projects.github.io/micronaut-aws/snapshot/guide/#sdkv2 Will be in the Micronaut 2.0 RC1 out in the next couple of weeks. |
While cross-checking found that our other services using Micronaut(1.3.4) and AWS SDK V2(SSM, Lambda&S3) working fine, This function also have same version dependencies and same native-image.properties but We have added elastic search client dependencies as given
look like Elastic Search Client jar has created native build issue, do i need to include any native-image.properties to solve this issue. Are we getting AWS SDK V2 support in Micronaut 1.3.X ? Codebase :- my-app-elasticsearch.zip |
Will try to get an example of this. Need to flatten some of our structure to produce an example. |
@ilopmar, do you have any maven projects for graal testing? |
@brianwyka No, I don't. You can easily create one using https://micronaut.io/launch/ or with the CLI (Micronaut 2.0.0.M3):
|
Hi @ilopmar, is there issue to build graal native image with Micronaut 1.3.4 and elasticsearch(6.7.1)? we are geeting following issue while upgrading micronaut(1.1.1) to micronaut(1.3.4) 81 | com.oracle.svm.core.util.UserError$UserException: Classes that should be initialized at run time got initialized during image building: Ref Code :- my-app-elasticsearch.zip |
Another user reported this micronaut-projects/micronaut-elasticsearch#34 with Micronaut 2.0.0.M3 an ElasticSearch 7.6.2. It's not the same error though. |
Above issue with Micronaut 2.0.0.M3, we are getting Issue with Micronnaut(1.3.4) and ElasticSearch(6.7.1). please refer RefCode :- my-app-elasticsearch.zip |
@msandy10 I've added support for Elasticsearch in GraalVM. Please take a look at micronaut-projects/micronaut-elasticsearch#34 (comment). Please be aware that you need to use I'm closing this issue because it's related to AWS and Elasticsearch and both work with GraalVM. If the problem persist, please open a new issue in the appropriate repository with a test application that reproduces the problem. |
Getting errors generating native image for micronaut
1.3.5
with nettyNetty 4.1.48.Final
.Please see attached
native-image.zip
for details about micronaut and third party native image configuration.native-image.zip
Some possibly related issues:
Task List
Steps to Reproduce
native-image.properties
Expected Behaviour
The native image should be created without any errors during building.
Actual Behaviour
When trying to create the native image, receive the following exceptions:
Environment Information
1.3.5
2.0.0
1.8
3.6.1
The text was updated successfully, but these errors were encountered: