I believe this only comes into play if you are using query caching. We
had to turn that off for this very reason.
[mailto:firstname.lastname@example.org] On Behalf Of Emmanuel
Sent: Sunday, November 11, 2007 5:29 PM
To: Markus Heiden
Subject: Re: [hibernate-dev] Memory consumption
You're missing one part, how about custom event listeners. Hibernate
Search used to use those events and needed the entity instances for
For the optimization, the JIRA issue has not been created AFAIK.
On Nov 11, 2007, at 17:00, Markus Heiden wrote:
> You need it for the post commit insert event.
I know, but during the execution of "post commit" code of the
EntityInsertAction only the id of the instance is needed and this
should be retrievable after a flush. So in all cases there is no
need to keep the reference to the instance after flushing.
> But we could optimize that if there is no such event.
Anyway this solution would be sufficient for first. Or does
hibernate keeps references to instances after a flush somewhere
Shall I create a JIRA issue?
hibernate-dev mailing list