Hibernate version: 3.2.5

Full stack trace of any exception that occurs:

10.04,14:59:23 [LoadContexts.java] WARN - fail-safe cleanup (collections) : org.hibernate.engine.loading.CollectionLoadContext@1047910<rs=org.apache.tomcat.dbcp.dbcp.DelegatingResultSet@641d52>
10.04,14:59:23 [LoadContexts.java] WARN - fail-safe cleanup (collections) : org.hibernate.engine.loading.CollectionLoadContext@a81958<rs=org.apache.tomcat.dbcp.dbcp.DelegatingResultSet@a6ff2>
10.04,14:59:23 [LoadContexts.java] WARN - fail-safe cleanup (collections) : org.hibernate.engine.loading.CollectionLoadContext@1047910<rs=org.apache.tomcat.dbcp.dbcp.DelegatingResultSet@641d52>
10.04,14:59:23 [LoadContexts.java] WARN - fail-safe cleanup (collections) : org.hibernate.engine.loading.CollectionLoadContext@a81958<rs=org.apache.tomcat.dbcp.dbcp.DelegatingResultSet@a6ff2>
10.04,14:59:23 [LoadContexts.java] WARN - fail-safe cleanup (collections) : org.hibernate.engine.loading.CollectionLoadContext@1047910<rs=org.apache.tomcat.dbcp.dbcp.DelegatingResultSet@641d52>
10.04,14:59:23 [LoadContexts.java] WARN - fail-safe cleanup (collections) : org.hibernate.engine.loading.CollectionLoadContext@a81958<rs=org.apache.tomcat.dbcp.dbcp.DelegatingResultSet@a6ff2>
10.04,14:59:23 [LoadContexts.java] WARN - fail-safe cleanup (collections) : org.hibernate.engine.loading.CollectionLoadContext@1047910<rs=org.apache.tomcat.dbcp.dbcp.DelegatingResultSet@641d52>
[..]

Name and version of the database you are using: Oracle 9.2.0.6, pooling via DBCP

Hi,

we are facing an endless loop in LoadContexts.cleanup(). As you can see there are only 2 ResultSets which should get cleaned, but they were never cleaned and live forever in the collection. This generates a fair amount of CPU time and our logs look quite horrible....

Can anyone give us a hint whats wrong there. It just happens at some certain point of time and then it never ends. Who is triggering the cleanup? DBCP?

Marc Logemann