Message:
The following issue has been closed.
Resolver: Gavin King
Date: Thu, 25 Sep 2003 2:46 PM
I'm pretty certain that the cause of this is that the after completion callbacks are stored until the transaction completes. You should split this work across multiple transactions,
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-343
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-343
Summary: Session.clear() not clearing saved objects
Type: Bug
Status: Closed
Priority: Major
Resolution: REJECTED
Project: Hibernate2
Components:
core
Versions:
2.1 beta 3
Assignee:
Reporter: Robson Miranda
Created: Wed, 17 Sep 2003 3:40 PM
Updated: Thu, 25 Sep 2003 2:46 PM
Environment: RedHat Linux 9, j2sdk 1.4.2
Description:
I am having a problem with Session.clear(). It seems that, when doing
PersistentObject o = new PersistentObject();
o.setRelation(session.load(OtherPersistentObject.class, idOfOtherObject));
session.save(o);
session.flush(o);
session.clear(o);
the session cache is not cleared. I'm having OutOfMemoryExceptions when doing this loop several times.
When I remove the session.save(o), everything works fine.
----
Robson
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
