Menu
I have been searching a lot to identify how spring JPA closes EntityManager connection after opening it. I have used @PersistenceContext to inject Transactional EntityManager to my DAOs and this implies that spring will take care of creating and closing EntityManager for me. However in my previous implementation I used to create and close EntityManager from DAOs, which is now replaced using spring. Can anybody please help me to understand, does spring close the EntityManager Connection once transaction is over or it maintain till the application is disposed?
FYI, I am not closing the EntityManager of my own assuming spring will close it for me once transaction is over. I fear if not it will lead to resource leak at some point of time.
Regards Rajib
588
public boolean isOpen (); public void close ();
Creating an EntityManagerFactory is a pretty expensive operation and should be done once for the lifetime of the application (you close it at the end of the application). So, no, you should not close it for each persist/update/delete operation.
EntityManager is part of the Java Persistence API. Chiefly, it implements the programming interfaces and lifecycle rules defined by the JPA 2.0 specification. Moreover, we can access the Persistence Context by using the APIs in EntityManager.
The EntityManager becomes closed as soon as an SQL exception is thrown by the underlying connection. The "real" exception has surely occurred before that. You will need a new EntityManager.
You may find this link useful. Also, from what I understand, when using the @PersistenceContext annotation, by default the entity manager is only attached for the duration of a method annotated with @Transactional and is closed automatically at the end of the method.
157
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
