We also get these a lot after our upgrade to seam 2.1.0.GA.
Unfortunately it does not help upgrading the hiberate.jar to the latest version either (I did this since there are indications in the HHH-Jira that this printout is a bug which has been fixed in later versions).
Actually I was wrong. This message (which we also got alot of recently) has nothing to do with Seam 2.1.0.GA as I suggested above. You see, at the same time as I changed seam versions I also made a minor change to one of our annotations.
I made a collection EAGER as this:
@OneToMany(mappedBy = "company", cascade = ALL, fetch = EAGER)
This gave the warning in our logs.
If also adding
@Fetch(value = SELECT)
... the error goes away. I doubt that this is a SEAM-bug. I would guess Hibernate.
My Warring Message is like bellow: What should I do?
WARN [LoadContexts] fail-safe cleanup (collections) : org.hibernate.engine.loading.CollectionLoadContext@c84d9d<rs=oracle.jdbc.driver.OracleResultSetImpl@16903c0>
The problem I think is from hibernate when you fetch a collection without elements, if you insert an element in the collection the problem dissapear. Try it to verify that.
I read somewhere that it is a bug in hibernate and it was solved in hibernate 3.2.6 a higher. I hope it helps you and forgive my english.