Key based Map Listener Fails To Reconnect After Losing Connection To Cluster
(Doc ID 1922434.1)
Last updated on NOVEMBER 03, 2016
Applies to:Oracle Coherence - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
In Coherence, a key based MapListener can be registered with a cache. This listener only fires for the desired key have changes, see ObservableMap.addMapListener.
Key-based map listeners can stop receiving events under two scenarios:
- All the storage cache servers in the cluster are restarted while the storeage-disabled nodes, which have registered key-based map listeners, are left running.
- A client application is disconnected and re-connects through a different extend proxy.
Once these situations are encountered, the client that registered the map listener stops receiving events. Note that the first scenario is highly unusual, and isn't typical of the normal production operation of a Coherence cluster.
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