cache.coordination.propagate-asynchronously

Use eclipselink.cache.coordination.propagate-asynchronously to specify if the coordination broadcast should occur asynchronously with the committing thread

property configures cache coordination for a clustered environment. Set if the coordination broadcast should occur asynchronously with the committing thread. This means the coordination will be complete before the thread returns from the commit of the transaction.

Values

Table 5-11 describes this persistence property's values.

Usage

JMS cache coordination is always asynchronous, regardless of this setting.

By default, RMI cache coordination is asynchronous. Use synchronous (eclipselink.cache.coordination.propagate-asynchronously = false) to ensure that all servers are updated before the request returns.

Examples

Example 5-5 shows how to use this property in the persistence.xml file.

<property name="eclipselink.cache.coordination.propagate-asynchronously" value="false" />

See Also

For more information, see:

• "cache.coordination.protocol"

• "Cache Coordination" in Understanding EclipseLink

• "Scaling EclipseLink Applications in Clusters" in Solutions Guide for EclispeLink