Skip Headers

# Configuring the Synchronous Change Propagation Mode

Previous

Next

You can configure whether the coordinated cache should propagate object changes asynchronously or synchronously.

Table: Coordinated Cache Support for Propagation Mode Configuration summarizes which coordinated caches support propagation mode configuration.

Coordinated Cache Support for Propagation Mode Configuration

Coordinated Cache | Using TopLink Workbench | Using Java
--- | --- | ---
JMS Coordinated Cache (asynchronous only) |  |
RMI Coordinated Cache |  |
CORBA Coordinated Cache |  |
Custom Coordinated Cache |  |

Synchronous propagation mode forces the session to wait for an acknowledgement before sending the next object change notification: this reduces the likelihood of stale data at the expense of performance.

Asynchronous propagation mode allows the session to create separate threads to propagate changes to remote servers. TopLink returns control to the client immediately after the local commit operation, whether or not the changes merge successfully on the remote servers. This offers superior performance for applications that are somewhat tolerant of stale data.

For more information, "Handling Stale Data".