[hibernate-issues] [Hibernate-JIRA] Closed: (HHH-2795) CollectionLoadContexts for empy collections are not removed until PersistenceContext.clear()
Gail Badner (JIRA)
noreply at atlassian.com
Sun Aug 19 19:12:13 EDT 2007
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gail Badner closed HHH-2795.
----------------------------
> CollectionLoadContexts for empy collections are not removed until PersistenceContext.clear()
> --------------------------------------------------------------------------------------------
>
> Key: HHH-2795
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2795
> Project: Hibernate3
> Issue Type: Bug
> Affects Versions: 3.2.5
> Reporter: Gail Badner
> Assignee: Gail Badner
> Fix For: 3.2.6, 3.3
>
>
> A CollectionLoadContext is created for an empty ResultSet but is not registered with LoadContexts. This causes CollectionLoadContexts.endLoadingCollection() too return early without removing the CollectionLoadContext().
> As a result, the CollectionLoadContext is not removed until PersistenceContext.clear() is called which calls LoadContexts.cleanup(). When a CollectionLoadContext is still in present, LoadContexts.cleanup() writes a warning to the log, as mentioned in HHH-2631.
> This is reproduced by org.hibernate.engine.loading.MergeTest.testNoExtraUpdatesOnMergeWithCollection() as well as other unit tests.
--
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