Coherence Interceptor Fires For Wrong Cache
Last updated on JUNE 27, 2018
Applies to:Oracle Coherence - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
Two Coherence clusters with federation set up between them to replicate information from certain caches between the clusters. Interceptors are used to ensure new records are not overwritten with older records from the other cluster during federation. However, one of the interceptors is fired during federation for a cache for which it is not configured, leading to an exception being thrown and the federation being incorrectly aborted. The intereceptor is called RetainMostRecentVersionInterceptor and is triggered during COMMITTING_REMOTE Federated Change Events.
This problem seems to be caused by several caches being located in the same scheme (federated-admin-scheme). Of those caches, three are being federated (users, desks and federation-beacon). The interceptor (RetainMostRecentVersionInterceptor) is configured to fire only for the users and desks cache, using the configuration method described in section "188.8.131.52 Registering Event Interceptors For a Specific Cache" of the Coherence development guide. However, it clearly fires during federation of federation-beacon cache records as well.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms