Anyone knows if the Session.saveOrUpdateCopy call causes memory leak?
We have the following persistent object model:

class A {
Set Bs; // A has a one-to-many relationship with B
}

class B {
A a; // many-to-one side of A
}

Somehow, we ran into a case (after the following code):

A a = session.saveOrUpdateCopy(A);

The new A object saveOrUpdateCopy() returns has a new B, but the new B object is referencing back to the old A (instead of the A returned by saveOrUpdateCopy). So the old A was never garbage collected. Anyone knows what would cause it? Is it a known problem? Any workaround?

Thanks,
--Jiunjiun


[b]Hibernate version:[/b]
2.1.7

[b]Mapping documents:[/b]

[b]Code between sessionFactory.openSession() and session.close():[/b]

[b]Full stack trace of any exception that occurs:[/b]

[b]Name and version of the database you are using:[/b]
postgres 7.x

[b]The generated SQL (show_sql=true):[/b]

[b]Debug level Hibernate log excerpt:[/b]