[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2393?page=c...
]
Steve Ebersole commented on HHH-2393:
-------------------------------------
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.
Generated properties leave open ResultSet on Batcher to be closed on
transaction completion
-------------------------------------------------------------------------------------------
Key: HHH-2393
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2393
Project: Hibernate3
Type: Bug
Components: core
Versions: 3.2.0.ga
Reporter: Steve Ebersole
Assignee: Steve Ebersole
Priority: Trivial
Fix For: 3.2.3
The patch for HHH-1750 was not complete...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira