Hi Yu Wang,
I'm not sure how to configure Spring to not cache the EntityManager. My
guess is that Spring would cache an EntityManager for the lifetime of a
transaction and then close it at the end of the tran. The best reference I
could find is here [1].
Using an entirely new
Hi Mike,
Following is how I close cache:
property name=openjpa.DataCache value=false /
property name=openjpa.QueryCache value=false /
property name=openjpa.jdbc.QuerySQLCache
value=false /
Hello,
My application uses Tomcat6,derby,spring and OpenJPA 1.20.
My case is stopping derby database and restarting it. And I found even
if I catch the database connection broken exception and create an new
EntityManager successfully after derby restarts, the following
exception stack will be