AutomaticCacheCoherency
String
ServerDefault
Purpose
The AutomaticCacheCoherency parameter specifies whether objects in the object cache of a client node are always current; for example, so that you do not have to explicitly implement a caching strategy in your applications. The default value of ServerDefault enables cache coherency only if the AutomaticCacheCoherencyDefault parameter in the [JadeServer] section on the server node is set to true.
Set this parameter to true in the JADE initialization file used by the client node if you want to enable client cache coherency. When this parameter is set to true, cache synchronization is enabled, regardless of the setting of the AutomaticCacheCoherency parameter in the [JadeServer] section on the server node.
Set this parameter to false in the JADE initialization file used by the client node if you want to disable client cache coherency. When you set this parameter to false, cache synchronization is not enabled, regardless of the setting on the server.
Parameter is read when …
The application server or the standard (fat) client node is next initialized.
Notes
With automatic cache coherency, an object updated on another node is automatically reloaded in cache, even when it is the receiver of a method currently being executed.
An out-of-date object can still be accessed even when cache coherency is enabled if the object is retrieved from the local cache while it us being updated by another node.
You can guarantee that an object is not being updated by another process only by locking it. (An out-of-date object can still be accessed while an update (or delete) notification is ‘in transit’.)
When automatic cache coherency is enabled, calling the
