Eclipse Community Forums: EclipseLink » No Cache Synchronization after em.clear?

Home » Eclipse Projects » EclipseLink » No Cache Synchronization after em.clear?

No Cache Synchronization after em.clear? [message #642535]

Wed, 01 December 2010 12:34

Eclipse User

Is it intended in eclipselink that after you execute an em.flush() and afterwards an em.clear() in a transaction no more cache synchronization can happen? We've run into this issue and analyzed for several hours why no synchronization messages are generated.

Can anybody maybe shed some light on this?

Re: No Cache Synchronization after em.clear? [message #642803 is a reply to message #642535]

Thu, 02 December 2010 13:19

Eclipse User

This is controlled by the "eclipselink.flush-clear.cache" persistence unit property. The modes are defined in FlushClearCache, the default is DropInvalidate which will not maintain change sets across a clear. You can set it to Merge to keep the change sets.

The reason is that clear is normally used after a flush to process large transactions, where keeping the change sets until the commit would not be feasible, so they are dropped by default.

Technically we should invalidate the entire remote cache with DropInvalidate with cache coordination. You can log a bug for that.

Previous Topic:	Shared Cache not working when using eclipselink with Spring
Next Topic:	Subqueries using ExpressionBuilder

Goto Forum:

-=] Back to Top [=-

Current Time: Wed Jul 23 07:26:22 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter