I can get the logs of (org.hibernate.orm.jdbc.extract) but I do not have much idea how to read them.
Also, is the graph building by hibernate safe for concurrent modifications while reading?
What I am observign is that ssertion error is happeing on separate thread, where we iterate over all account anytime something changes in database.
So in main thread we setup our associations, one-by-one without transaction.
When hibernate builds the graph it issues several queries. Could it be that assosciation appering in between those queries makes the assert assumption wrong?
The error is happeing spradicaly, it will be a major effort to distill the correct setup for exact reproduction. I was trying to force it by making paralle loads more often, but couldnt really find a pettern.
Would you make a use of those org.hibernate.orm.jdbc.extract logs?
findAll() is called without encompassing transaciton and hibernate session, so everything in hibernate context should be fresh. How is it even possible that we get different initializers?