Cache Service Starting Up Unintentionally On Nodes
(Doc ID 793467.1)
Last updated on JANUARY 16, 2023
Applies to:Oracle Coherence - Version 3.3.1 to 3.4.2
Information in this document applies to any platform.
This problem can occur on any platform.
Having two different cache services defined in cache-configuration.
To control what nodes the above services should be on, system-property defined in cache-config.xml was used.
So, from the configuration it is required to start OTCCacheStoreService on only two nodes dedicated for that service (nodeid-13, nodeid-25). But it was found out that the service
OTCCacheStoreService has also been running on 3 other nodes dedicated for another service called 'OTCCacheNotifyService'( nodeid-39, nodeid-43, nodeid-66).
Why did the service OTCCacheNotifyService start up on ( nodeid-39, nodeid-43, nodeid-66)?
This behavior is causing the nodes 39/43/66 to store data that belongs to the service OTCCacheStoreService, whereas these 3 nodes are dedicated nodes designed to store data that belongs to only OTCCacheNotifyService.
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