About cache

11-20 of 200Refresh


Method javax.persistence.Cache void evictAll() Clear the cache. Since: JPA 2.0


Static Field javax.jdo.Constants String PROPERTY_IGNORE_CACHE "javax.jdo.option.IgnoreCache" Since: JDO 2.1 See Also: PersistenceManagerFactory.getIgnoreCache()

ObjectDB Object Database Features

managed by EntityManagerFactory. Configurable - minimum/maximum connections and timeout. Caching L1 entity object cache (per EntityManager). L2 shared entity data cache (per EntityManagerFactory). Database file page cache. Query program cache (for repeating queries with different arguments). Query

Soft Reference Object Cache Recommendation

be cached until the Java Virtual Machine (JVM) does a full Garbage Collection (GC) when heap RAM gets low ... [] and instruct ObjectDB to use soft reference for its Level One (L1) object data cache.  I disable the L2 cache and use 1 MB for the ObjectDB Datastore page file cache with page file size of 64 KB

Database Explorer

of elements. Use the [First] and [Max] fields to set the result range. Check [Disable Cache] to bypass query program and result caches. Click the Execute button to run the query. If the query is valid ... the Cache When a database is open in the Explorer in client server mode, it can be accessed simultaneously

Cache usage

after a runtime of several weeks we are now analyzing the usage of the cache and so on. Looking at the heap dump we suspect that the cache is really used (see heap dump attached), the RAM allocated ... . The config is attached as well. The question is: is the cache really used ? The heap dump shows usage

Level 2 cache not hit in @ManyToOne

2 JPA cache is activated and it works ok for find by id (tested by changing data in explorer and reading in my app). Problem 1: find by id on Item it's good, it hits the cache, but not for its field ... my app). "user" should also be taken from L2 cache, shouldn't it? Otherwise...it's a huge performance

Is 2 level cache in use?

Hi, Is there any way to check, if 2 level cache is in use? Right now I've done two things: 1. objectdb.conf with cache size is placed in WEB-INF directory of my web application. 2. persistence.xml ... , so most of the data should be in cache. ODB and Tomcat are on different servers. You cannot check

JQL-Update Queries fails with activated L2-Cache

a container the updated Entities. Scenario 1: Disabled L2 Cache, updating elements using UPDATE-Query ... database - Actual result: No changes are visble. Scenario 2: Disabled L2 Cache, updating elements using ... a mystery why ".clear()" has to be called. Scenario 3: Enabled L2 Cache, updating elements using UPDATE

Enforce Second Level cache

that is cached in 2nd level cache. so that if i request that entity again I will get actually ... on this (is it really the same object kept in cache).... Now the problem is that I need to have guarantee that this entity object is kept in cache all the time (there are not many of these entities