Coherence .Net Clients Are Not Reconnected With Coherence Servers When One Of The Node Gets Rebooted
(Doc ID 2290643.1)
Last updated on SEPTEMBER 13, 2021
Applies to:Oracle Coherence - Version 18.104.22.168 and later
Information in this document applies to any platform.
Coherence Clients are connected to Coherence Servers via Load Balance Points. And F5 LBP as connecting as Round Robin to each coherence servers. Coherence Clients are not reconnected with Coherence Servers when one of the Proxy node gets rebooted.
Customer have one of 4 servers in PROD Coherence Clusters using multicast address. One of our Coherence server getting rebooted , Coherence client is not getting connected other available Proxy servers instead its still stuck with rebooted server.
One of the Coherence servers gets rebooted... Clients are always struck with those rebooted servers until it gets completed. its happening in PROD region. To resolved the issue, Clients servers customers are doing IIS reset to reconnect. Issue happening only with .Net clients when they start the Proxy server. Issue not seen with Java Clients.
Issue happening only with .Net clients when they start the Proxy server. And issue is also seen with the first client request after the Proxy server is stopped. Once the client is able to establish the connection, then the issue is not seen with the subsequent client connections.
The connection is successful only if Open= true
First Attempt with Open as False and the Client request gets redirected to another proxy node.
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