Eclipse Community Forums: EclipseLink » Objects still exists after commit

Home » Eclipse Projects » EclipseLink » Objects still exists after commit

Objects still exists after commit [message #989942]

Mon, 10 December 2012 02:43

Eclipse User

Hello, everyone.

My situation is as follows:

My dao class is defined like the following:

class JpaDao extends JpaDaoSupport{

......

public insert(Object obj){
getTemplate().getEntityManager().persist(obj);
}

public merge(Object obj){
getTemplate().getEntityManager().merge(Object obj);
}

public detach(Object obj){
getTemplate().getEntityManager().detach(obj);
}
}

In my program, I used the class to persist objects. After I commited the transactions and detached my objects persisted or merged by the above class, there's still a lot of copies of my objects exists in memory, which led to a high memory usage. I used jprofiler to debug the program and discovered that all these copies are referenced by "UnitOfWorkCacheKey" or "RepeatableWriteUnitOfWork" objects.

Is this normal? How can I delete these copies from memory?
Thanks.

[Updated on: Mon, 10 December 2012 20:15] by Moderator

Re: Objects still exists after commit [message #990300 is a reply to message #989942]

Tue, 11 December 2012 13:27

Eclipse User

It sounds like you are still holding onto the EntityManager. The EntityManager represents a single persistence context, they should not live beyond a transaction or request.

Previous Topic:	EQL / JPQL Operator -datepart- Usage
Next Topic:	JPQL query with ElementCollection throw exception

Goto Forum:

-=] Back to Top [=-

Current Time: Fri Jul 25 20:19:00 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter