NOTE: This article is 3 years or older so its information may no longer be relevant. Read on at your own discretion! Comments for this article have automatically been locked, refer to the FAQ
for more details.
While working on a web service that used Oracle Coherence
to cache some data I encountered the following error during deployment...
My web service's coherence-cache-config.xml
file didn't specify any LocalCache
configuration however, which means it was simply inheriting it from the system-wide configuration and that was causing a conflict.
To stop this conflict all I had to do was add a <scope-name>
configuration element to the <cache-config>
element like so...
The above is documented here
Specifies the scope name for this configuration. The scope name is typically used (as a prefix) for all services generated by a cache factory to isolate services indicated in this cache configuration from services created by cache factories with other configurations, thus avoiding unintended joining of services with similar names from different configurations.
A quick disclaimer...
Although I put in a great effort into researching all the topics I cover, mistakes can happen.
If you spot something out of place, please do let me know.
All content and opinions expressed on this Blog are my own and do not represent the opinions of my employer (Oracle).
Use of any information contained in this blog post/article is subject to this disclaimer
Other posts you may like...