sion.flush() and Session.evict() to get rid of these objects each
1000 objects, because the memory usage was too high. But for the above
reason I had no chance to succeed. The workaround was to commit the session
more often, but this breaks transactional behaviour.
Any thoughts?
Mar
.
Markus Heiden
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
nce 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 else too?
Shall I create a JIRA issue?
Mar
this problem too (at
least if the Entity*Actions have hasAfterTransactionCompletion() == false),
because the Entity*Actions aren't cached at all in ActionQueue.executions
(as you already described).
Markus Heiden
___
hibernate-dev mailing list
