Replicated Cache Lacks Xsd Or Runtime Validation With Cachestore [COH 3.3 to 3.7]
(Doc ID 1400683.1)
Last updated on FEBRUARY 15, 2023
Applies to:Oracle Coherence - Version 3.3.0 to 22.214.171.124
Information in this document applies to any platform.
From COH 3.3 to Coherence 3.7
Fixed Version 126.96.36.199
It is not recommended to implement Replicated cache as the Cache store per the document below :
For use with Partitioned (Distributed) and Near cache topologies: Read-through/write-through caching (and variants) are intended for use only with the Partitioned (Distributed) cache topology (and by extension, Near cache). Local caches support a subset of this functionality. Replicated and Optimistic caches should not be used.
However the XSD fails to validate this. There is also no runtime message, and this unsupported configuration fails silently.
It appears that the invalid configurations are not picked up by the XSD validation during build, and we observe that there are no error messages at runtime.
The requirement is that Coherence should validate any configuration misses since this is the objective of using XSD validation.
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