-
Notifications
You must be signed in to change notification settings - Fork 40.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
Migration from Spring Boot 3.1.5 to 3.2.0 HibernateSearch Index Building fails #38585
Comments
This looks as if it may be caused by the new nested jar support. Can you please try with the classic loader implementation and let us know if the problem still occurs? A minimal sample that reproduces the problem would also be very useful. |
Thank you very much for your advice. Since we use spring-boot-starter-parent we added <plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<executions>
<execution>
<id>repackage</id>
<configuration>
<loaderImplementation>CLASSIC</loaderImplementation>
</configuration>
</execution>
</executions>
</plugin> to our maven pom and could successfully start our application again. |
I'm struggling to reproduce the exact failure you are experiencing, @ajobra76. I have managed to trigger the following failure:
As you will see, it's not exactly the same as yours. A minimal example that reproduces the |
If you're not using Jandex indexes, I think you can work around the problem with the following bean:
And this configuration property to enable its use:
|
#38595 should have hopefully fixed the problem with reading the CEN tables. That fix is in the latest 3.2.1-SNAPSHOT build that's available from https://repo.spring.io. Could please give it a try with the new default (not classic) loader implementation? |
... we tested the snapshot 3.2.1version. It seems to be now a different Error
|
I have the same error with 3.2.0:
|
I think we're going to need to ask the Hibernate Search team if they can refine their nested jar support code. It looks like this code is problematic when there's only a single Our new JAR url format is Reading the hibernate code I think @don-vip or @ajobra76, would one of you mind raising this on the Hibernate issue tracker please? |
In the meantime, you can switch back to the classic loader implementation, details of how to do that are here. |
…ing-boot:run by defaults starts tomcat, while the jetty profile enables jetty added a fix to run the generated war with spring-boot on tomcat, due to issues with spring-boot 3.2.0 spring-projects/spring-boot#38585 the jar generated with jetty doesn't work at the moment
The text was updated successfully, but these errors were encountered: