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.
Hope you found this post useful...
...so please read on! I love writing articles that provide beneficial information,
tips and examples to my readers. All information on my blog is provided free of
charge and I encourage you to share it as you wish. There is a small favour I ask in return however -
engage in comments below, provide feedback, and if you see mistakes let me know.
If you want to show additional support and help me pay for web hosting and
domain name registration,
donations, no matter how small, are always welcome!
Use of any information contained in this blog post/article is subject to this disclaimer
Other posts you may like...