Urs Keller ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiOWIyMDgyZDZj... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16199?atlOrigin=eyJpIjoiOWIyMD... ) HHH-16199 ( https://hibernate.atlassian.net/browse/HHH-16199?atlOrigin=eyJpIjoiOWIyMD... ) org.hibernate.AssertionFailure: force initializing collection loading ( https://hibernate.atlassian.net/browse/HHH-16199?atlOrigin=eyJpIjoiOWIyMD... ) Issue Type: Bug Affects Versions: 6.0.2, 6.2.0.CR2, 6.1.7 Assignee: Unassigned Created: 18/Feb/2023 08:24 AM Priority: Major Reporter: Urs Keller ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) We have some code not behind a @Transactional but using ad-hoc transactions. On some weird constellation with bidirectional many-to-one and one-to-one and circular graph, we get this assertion to trigger: org.hibernate.AssertionFailure: force initializing collection loading The stripped-down reproducer project is here: https://github.com/ls-urs-keller/hibernate-force-initalizing-collection-p... ( https://github.com/ls-urs-keller/hibernate-force-initalizing-collection-p... ) There is a single Test class that has 2 test methods one fails the other works. I haven’t completely stripped out the spring dependencies, I hope that is OK and it won’t turn out to be a spring problem. This relates to the discussion here: https://discourse.hibernate.org/t/force-initializing-collection-loading/7172 ( https://discourse.hibernate.org/t/force-initializing-collection-loading/7172 ) ( https://hibernate.atlassian.net/browse/HHH-16199#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16199#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=Em... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100216- sha1:3fa9804 )