Today I made another step towards migration end. The project is compiled and indexing process starts. At some point I get an exception: org.hibernate.AssertionFailure: force initializing collection loading The full indexing log is here . Another issue I have is with my Provider class I mention…

I have filed a Jira here [HHH-16199] - Hibernate JIRA , it includes a link to a reproducer project.

[image] horvoje: org.hibernate.AssertionFailure: force initializing collection loading This looks like a bug in Hibernate ORM 6.1. If you can report it on Jira with a reproducer, we will have a look. Maybe try with Hibernate ORM 6.2.0.CR1 first, in case this has already been fixed? [image…

[image] yrodiere: You are accessing a field directly, which sidesteps Hibernate proxies and lazy initialization. Use a getter instead and everything should be fine: Thanks! If I were thinking, I would have to come to this on my own. Changed it to use getter and now this part is working as e…

Tried to update dependencies to give a try 6.2.0.CR1, but no luck - app won’t start. Exception is thrown in early stage of boot attempt: java.lang.IllegalStateException: Cannot apply class transformer without LoadTimeWeaver specified Log is available here . CurrencyRepositoryImpl.java import …

Looks like a Spring problem, probably unrelated. You’d better report your previous problem on JIRA then, even if you can only reproduce it on 6.1. Please include a (minimal) reproducer though (ZIP file containing the source code or link to a github repository). Ideally you’d use the templates availa…

To create reproducer it would take days - perhaps the only way would be to copy the whole project to new one and then cut out class by class to minimize it. I’ll contact you with message if I find how to and suggest another way.

Just for test purposes I replaced all fetch = FetchType.LAZY with fetch = FetchType.EAGER (I have it on 29 places in project) and the exception is still the same: org.hibernate.AssertionFailure: force initializing collection loading Now I’m thinking that could be endles loop because I have back …

@yrodiere Can’t understand why, but when I forced all my relations to LAZY, indexing is finished successfully. Before I had 29 LAZY relations and 3 EAGER relations (user roles to user and two similar). [xxx] As I switched to new Spring Boot and new Hibernate also, I have some issues with Thymelea…

Yes, this is most likely a bug in Hibernate ORM 6.1 not handling association loading correctly in your particular case. As is obvious from the ORM 6 migration guide , a lot of things changed in ORM 6 and thus different bugs were to be expected. If you want this fixed, you will need to identify the p…

Force initializing collection loading

Hibernate Search

Topic		Replies	Views
Lazy initialization exception on mass indexing/intial indexing Hibernate Search	2	1227	October 1, 2018
Query execution extremely slow after upgrading to Hibernate ORM 6.2 Hibernate ORM	36	5674	June 6, 2023
java.lang.AssertionError: in RepositoryMethodInvoker Hibernate ORM	8	143	December 12, 2025
Indexing lazy collection Hibernate Search	3	1090	September 24, 2018
Hibernate Search 6.0 - org.hibernate.search.util.common.AssertionFailure Hibernate Search	20	994	February 18, 2021

Force initializing collection loading

Related topics