Disable caching in JPA (eclipselink)

I want to use JPA (eclipselink) to get data from my database. The database is changed by a number of other sources and I therefore want to go back to the database for every find I execute. I have read a number of posts on disabling the cache but this does not seem to be working. Any ideas? I am trying to execute the following code:
EntityManagerFactory entityManagerFactory = Persistence.createEntityManagerFactory("default"); EntityManager em = entityManagerFactory.createEntityManager(); MyLocation one = em.createNamedQuery("MyLocation.findMyLoc").getResultList().get( 0); MyLocation two = em.createNamedQuery("MyLocation.findMyLoc").getResultList().get( 0);

up vote System.out.println(one==two); 13 down one==two is true while I want it to be false. vote favorit I have tried adding each/all the following to my persistence.xml e <property name="eclipselink.cache.shared.default" 6

value="false"/> <property name="eclipselink.cache.size.default" value="0"/> <property name="eclipselink.cache.type.default" value="None"/>

I have also tried adding the @Cache annotation to the Entity itself:
@Cache( type=CacheType.NONE, // Cache nothing expiry=0, alwaysRefresh=true )

Am I misunderstanding something? Thank you, James java jpa entity eclipselink

asked May 11 '10 at 8:59 share|improve this question edited May 11 '10 at 10:09 James 93052241 Please change the title ("chaching" is not "caching") Kartoch May 11 '10 at 9:03 James in your comment to my answer, was the caching off ( <property name="eclipselink.cache.shared.default" value="false"/> ) when you tested it? Justin May 11 '10 at 13:04 Sorry just noticed this, yes the caching was off. I am still having this issue and am no closer to a solution. James May 27 '10 at 11:39

4 Answers
active oldest votes This behavior is correct, otherwise if you change object one and object two with different values you will have problems when persisting them. What is happening is the call to load object two updates the entity loaded in the first call. They must point to the same object since they ARE the same object. This ensures that dirty data cannot be written. If you call em.clear() between the two calls, entity one should become detached your check will return false. There is however no need to do that, eclipse link is infact updating your data to the latest which I would guess is what you want since it frequently changes. up vote On a side note if you wish to update this data using JPA you will need to be obtaining pessimistic locks on the Entity so that the underlying data cannot 11 down change in the DB. vote accept You will need to disable the query cache as well your cache options were just removing the object cache from play not the query cache, that is why you are ed not getting the new results: In your code:
em.createNamedQuery("MyLocation.findMyLoc").setHint(QueryHints.C ACHE_USAGE, CacheUsage.DoNotCheckCache).getResultList().get(0);

Or in persistence.xml:
<property name="eclipselink.query-results-cache" value="false"/>

share|improve this answer

edited May 11 '10 at 13:20

answered May 11 '10 at 9:26

Justin 1,534718 That helps thank you. I will have to look at pessimistic locks as the data will be changing. How then if I add a Thread.sleep(10000) between the queries and in that time manually change an attribute of MyLocation in the database does two (and therefore one) not reflect this change? James May 11 '10 at 11:42 added a link to some info about pessimistic locks Justin May 11 '10 at 13:08 I have tried the described change in the code and persistence.xml and still don't get the value I changed directly. Any ideas? James May 12 '10 at 9:28

See, http://wiki.eclipse.org/EclipseLink/UserGuide/JPA/Basic_JPA_Development/Cac hing For the same EntityManager JPA always requires that one==two, so this is correct, not matter your caching options (this is the L1 cache, or transactional cache, which enforces your transaction isolation and maintains object identity). To force the query to refresh (and revert any changes you have made) you can use the query hint "eclipselink.refresh"="true". Or probably better, use a new EntityManager for each query/request, or call clear() on your EntityManager.

up vote <property name="eclipselink.cache.shared.default" value="false"/> 3 dow Is the correct way to disable the shared cache (L2 cache). Please remove all your n other settings as they are not correct, and can cause issues. vote

EclipseLink does not maintain a query cache by default, so those settings will have no affect. CacheUsage is also not correct, do not use this (it is for in-memory querying). answered Dec 5 '12 at 14:12 share|improve this answer James 13.7k1718

Note that "eclipselink.refresh"="true" is buggy in current versions of EclipseLink (bugs.eclipse.org/bugs/show_bug.cgi?id=398074); also, it is 1 EclipseLink-specific and not part of JPA. So I'd advise to just get a fresh EntityManager whenever you want fresh data - that's how it is supposed to work with JPA. sleske Jan 17 at 0:51 If manually modifying the attributes of the object, for example MyLocation. The above trick (CACHE_USAGE=CacheUsage.DoNotCheckCache, or eclipselink.query-results-cache=false) does not seem to work as I tried. So i tried to set another hint which is "eclipselink.refresh", to "true". then it works. I mean the manually changed attributes get retrieved. up vote 2 down vote So as i understand, the above trick only ensure the it gets the correct objects. However, if the objects have been cached already, eclipselink just returns them without checking the freshness of the contents of the objects. Only when the hint "eclipselink.refresh" is set to "true", will these objects get refreshed to reflect the latest attribute values. answered Aug 11 '10 at 0:22 share|improve this answer Robin 543 Hava you set this in your persistence.xml? If I add this hint to the query it 1 works. But it does not work if I define it only in my persistence.xml. Waxolunist Nov 29 '12 at 12:28 final Query readQuery = this.entityManager.createQuery(selectQuery); readQuery.setParameter(paramA, valueA); // Update the JPA session cache with objects that the query returns. Hence the entity objects //in the returned collection always updated. up vote 2 readQuery.setHint(QueryHints.REFRESH, HintValues.TRUE); down vote entityList = readQuery.getResultList(); This works for me. share|improve this answer