Steve Ebersole - 30/Jan/07 10:52 PM trunk / 3.2

Steve Ebersole - 31/Jan/07 07:06 AM Further clarification... This issue only shows up with after_statement release modes. The symptom is that the result set is kept around on the internal org.hibernate.jdbc.AbstractBatcher#resultSetsToClose queue after execution (even though it is closed). Then during org.hibernate.jdbc.ConnectionManager#afterTransaction processing, it sees the fact that the batcher still "holds a result-set" and logs a message ("forcing batcher resource cleanup on transaction completion; forgot to close ScrollableResults/Iterator?"). It then forces the batcher to close the resources (which in this case is the already closed result set). So to be clear it is just a problem with an inappropriate log message; the result set *was not* being leaked.