Native image does not start with Hibernate and Spring Boot 3.1.0 #35659
Comments
spring-projects-issues
added
the
status: waiting-for-triage
|
I am also experiencing this same issue/error. Here is an even more minimal reproducer that uses h2 instead of postgres: |
|
The Hibernate 6.2 upgrade was challenging. There are numerous issues in the Spring Framework issue tracker. I am going to close this now and please test against Spring Framework Duplicates spring-projects/spring-framework#30492 |
snicoll
added
status: duplicate
|
@snicoll I got it to work, but only after adding the following hints in a reflect-config.json: [
{
"name": "org.hibernate.dialect.DialectLogging_$logger",
"methods":
[
{
"name": "<init>",
"parameterTypes":
[
"org.jboss.logging.Logger"
]
}
]
},
{
"name": "org.hibernate.metamodel.mapping.MappingModelCreationLogging_$logger",
"methods":
[
{
"name": "<init>",
"parameterTypes":
[
"org.jboss.logging.Logger"
]
}
]
}
]Can we re-open this until it works out of the box w/ Spring Framework 6.0.10-SNAPSHOT? Also, how can I contribute some sort of testing around native with Hibernate? I am really pushing the use of native-image at my company, but things keep breaking between releases pretty often. |
|
Those hints are present in the current version of the reachability metadata, but I still had to add them to make it work. Maybe the compiler doesn't think they're reachable for some reason (I do see the 'typeReachable' field). |
|
@matthenry87 no, we can't reopen this issue as it is something that's Hibernate-specific. Check the reachability metadata repo, those might have been fixed in the meantime. If not, please report that there. |
Thanks for the response. Will open an issue over there. |
|
@matthenry87 can you please link that issue here, for reference? |
|
Also for reference: I got this to work without issuing additional type hints. I generated a new project using Spring Initializr (with Native, Data-JPA and H2), added the Spring Snapshot repo and set the I also explicitly configured the rechability metadata version to be used by the native plugin: I guess this is a good idea anyways. Still, I find it quite strange that the native maven plugin does pull metadata automatically but does not tell which version it used (not even when run in To be precise:
Thus, both are required. In other words, Spring Native is broken for applications using Hibernate in Spring Boot 3.1.0 and we need to wait for 3.1.1 that probably picks up Spring Framework 6.0.10 or later. |
I am not sure what you mean by that, but that conversation doesn't belong here.
There's no such thing as Spring Native anymore but, other than than, this is a rewrite of where we were initially. Yes, you need spring framework snapshot for now and, yes, you need a more recent metadata version as the one that shipped with the native maven plugin we use didn't contain the fix. |
I meant that I find it strange that it does not output the version of the used metadata. But you are right, this discussion does not belong here. I was just venting, sorry 😊 |
|
It's available from https://repo.spring.io/snapshot. If you have any further questions, please follow up on Stack Overflow or Gitter. As mentioned in the guidelines for contributing, we prefer to use GitHub issues only for bugs and enhancements. |
|
It's works if you change your SB to 3.0.0 when you use JPA and oracle. |
Why revert to 3.0.0 when you can just use the temporary fixes mentioned in this thread? Fix being usage of the snapshot (that has official fix), and pointing at the right hints. |
|
I try the 3.1.1-SNAPSHOT,but get a new exception. |
My application uses Spring Boot 3.1.0 and spring-data-jpa. When I build a native image using
mvn -Pnative native:compileand run the resulting image, I get the following error:The problem disappears when I manage the Hibernate version to 6.1.7 (or use Spring Boot 3.0.7).
spring-boot-native-example.zip
The text was updated successfully, but these errors were encountered: