Coherence*Extend Client Not Receiving Cache Updates When Used Near-Schemes
(Doc ID 2234093.1)
Last updated on DECEMBER 13, 2022
Applies to:
Oracle Coherence - Version 12.2.1.0.0 to 12.2.1.2.0 [Release 12c]Information in this document applies to any platform.
Symptoms
The customer did upgrade cluster from Coherence 3.7.1.x to 12.2.1.x.x. Customer did not see propagating cache updates to their existing Coherence*Extend clients. Previously before cluster upgrade to 12.2.1.x.x, if a cluster member updated a cache entry, that change would propagate to the extend client's front cache of the near-scheme. This is no longer happening. That is, if user update a cache entry on one node in the cluster, the user sees the change show up if user inspect that same key on any other node in the cluster. But if user inspect that key on the proxy client, it still has the old value.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |