Home » Search

About cache

61-70 of 200Refresh
JDO Doc
5

javax.jdo.identity.ObjectIdentity

. Since: JDO 2.0 int hashCode() Return the cached hash code. Return the cached hash code. Returns: the cached hash code. Since: JDO 1.0 void readExternal(ObjectInput in)throws IOException
JDO Doc
5

javax.jdo.identity.ShortIdentity

class name. Since: JDO 2.0 int hashCode() Return the cached hash code. Return the cached hash code. Returns: the cached hash code. Since: JDO 1.0 void readExternal(ObjectInput in)throws IOException
JDO Doc
5

javax.jdo.identity.SingleFieldIdentity

name. Since: JDO 2.0 int hashCode() Return the cached hash code. Return the cached hash code. Returns: the cached hash code. Since: JDO 1.0 void readExternal(ObjectInput arg0)throws IOException
JDO Doc
5

javax.jdo.identity.StringIdentity

.0 int hashCode() Return the cached hash code. Return the cached hash code. Returns: the cached hash
JDO Doc
5

javax.jdo.PersistenceManagerFactory

the DataStoreCache that this factory uses for controlling a second-level cache. Return the DataStoreCache that this factory uses for controlling a second-level cache. If this factory does not use a second-level cache, the returned instance does nothing. This method never returns null. Returns
JDO Doc
5

javax.jdo.spi.StateManager

( PersistenceCapable pc, int field) Return true if the field is cached in the calling instance. Return true if the field is cached in the calling instance. Parameters: pc - the calling PersistenceCapable instance field - the field number Returns: whether the field is cached in the calling instance
JPA Doc
5

javax.persistence.spi.PersistenceProviderResolver

that the implementation of this method make use of caching. Since: JPA 2.0 See Also: PersistenceProvider void clearCachedProviders() Clear cache of providers. Clear cache of providers. Since: JPA 2.0 List
JDO Doc
5

makeNontransactional(pc)

-transactional after commit. Normally, at transaction completion, instances are evicted from the cache. This method allows an application to identify an instance as not being evicted from the cache at transaction completion. Instead, the instance remains in the cache with nontransactional state
JDO Doc
5

setDetachAllOnCommit(flag)

the cache after commit is defined by the retainValues flag. With this flag set to true, during beforeCompletion all cached instances are prepared for detachment according to the fetch plan in effect ... callback, all detachable persistent instances in the cache transition to detached; non-detachable
Issue
5

Server out of memory exceptions

on the server side became higher mainly due to increasing page cache size. I see that the test uses 4 different databases (2 large and 2 small). The default size of each page cache (per database) is 64MB, so the cache of the two large databases consumes at least 128MB (probably a little more). Other caches