[hibernate-issues] [Hibernate-JIRA] Closed: (HHH-2602) instrumented many-to-one problem with aggressive release
Steve Ebersole (JIRA)
noreply at atlassian.com
Tue May 8 17:41:04 EDT 2007
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Ebersole closed HHH-2602.
-------------------------------
Resolution: Fixed
trunk / 3.2
> instrumented many-to-one problem with aggressive release
> --------------------------------------------------------
>
> Key: HHH-2602
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2602
> Project: Hibernate3
> Issue Type: Bug
> Components: core
> Reporter: Steve Ebersole
> Assignee: Steve Ebersole
> Fix For: 3.2.4
>
>
> There is a problem when using many-to-one with instrumentation in combination with aggressive release. The code to read an entity's lazy properties does not regiter the result set it opens with the batcher; if we then check for the ability to aggressively release a connection while we are still using the corresponding result set, the batcher says it is OK because it does not know about that ResultSet.
> Obviously the fix is to register the ResultSet.
--
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.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the hibernate-issues
mailing list