hum, you’re right and in the real codebase where I have the problem the associations are annoted with @Fetch(FetchMode.SELECT)

the problem also disappears when removing @Proxy(lazy=false) so now I think that the test case does not reproduce correctly the problem (because as you said fetch shouldn’t be eager)

I’ll try updating the test case with @Fetch(FetchMode.SELECT) and @Proxy(lazy=false)

thanks a lot for looking into it!