How frequently should I create an EntityManager?

java jpa entitymanager
AlBlue picture AlBlue · Nov 19, 2010 · Viewed 8.2k times · Source

I have an EntityManagerFactory for which I can create one (or multiple) EntityManager instances. I'm using a Servlet environment, and I've got one EntityManagerFactory wired up to the servlet (via the servlet context) which is shared for the lifetime of the servlet (and therefore, for all users).

I can do one of the following:

  • Create a single EntityManager for the lifetime of my servlet (e.g. shared between all users)
  • Create one per user (so each user gets their own in the HttpSession)
  • Create one per HTTP request (say, by instantiating a new one and closing it at the end of a doGet method)

Which is most appropriate? Is the cost of creating an EntityManager significant? If I do a single shared EntityManager, is there a single transaction scope (i.e. updates between independent users could commit others changes)?

Answer

Qwerky picture Qwerky · Nov 19, 2010

One EM for the whole servlet doesn't sound good. If you're not using container-managed EM's (for example EJB3) then the recommentation is to use an EM for a particular unit of work.

In a web application context your third suggestion (one per HTTP request) sounds good. However this may lead you down a pitfall where you are tying your service layer with your db layer (your service layer shouldn't even be aware of the existance of an EM).

Another approach would be to programatically demark transactions in your DAO and get your DAO to use a new EM for for every method call.

Edit: EMs are cheap to create as opposed to EMFs which have a significant overhead. Using one EMF (which it appears that you do) and lots of EMs is the way to go.

Related questions

What does EntityManager.flush do and why do I need to use it?

I have an EJB where I am saving an object to the database. In an example I have seen, once this data is saved (EntityManager.persist) there is a call to EntityManager.flush(); Why do I need to do this? …

Read More
What is the best way to update the entity in JPA

I am doing some CRUD operations using JPA. For updating an object which is the right way to do? Through update query or through the find method of EntityManager? I have one Employee object I need to update. Which is …

Read More
JPA merge vs. persist

So far, my preference has been to always use EntityManager's merge() take care of both insert and update. But I have also noticed that merge performs an additional select queries before update/insert to ensure record does not already exists …

Read More