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
doGetmethod)
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)?
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.
we do one injected entity manager for each slsb, - and the slsb is itself accessed via a delegate, of which there is one per session, which looks up the local/remote interface. Using ejb3.0.
Yes, I agree with NimChimpsky and Qwerky to use EJB3.x when accessing DBs and to use one EM per unit of work.
来源：https://stackoverflow.com/questions/4225638/how-frequently-should-i-create-an-entitymanager