Charging Nodes BufferedConnection CheckHealth Initiates Connection Migration After Timeout
(Doc ID 2610040.1)
Last updated on MAY 27, 2024
Applies to:
Oracle Communications BRM - Elastic Charging Engine - Version 11.3.0.6.0 and laterInformation in this document applies to any platform.
Purpose
There are messages on charging nodes in the passive site that indicate a connection migration:
Oct 24, 2019 8:05:16 AM com.oracle.common.internal.net.socketbus.AbstractSocketBus$HandshakeHandler$1 run
WARNING: tmb://IPAddress.51:20093.49833 accepting connection migration with tmb://IPAddress.6:20095.53758, replacing MultiplexedSocketChannel(MultiplexedSocket{Socket[addr=/IPAddress.6,port=20095,localport=60912]}) with MultiplexedSocketChannel(MultiplexedSocket{Socket[addr=/IPAddress.6,port=47800,localport=20093]}):
...
Oct 24, 2019 8:06:41 AM com.oracle.common.internal.net.socketbus.BufferedSocketBus$BufferedConnection checkHealth
WARNING: tmb://IPAddress.51:20093.49833 initiating connection migration with tmb://IPAddress.6:20095.53758 after 10s ack timeout health(read=false, write=true),
...
Oct 24, 2019 8:06:41 AM com.oracle.common.internal.net.socketbus.AbstractSocketBus$HandshakeHandler onIntroduce
WARNING: tmb://IPAddress.51:20093.49833 accepted connection migration with tmb://IPAddress.6:20095.53758 on MultiplexedSocketChannel(MultiplexedSocket{Socket[addr=/IPAddress.6,port=20095,localport=37220]}):
...
java.io.IOException: ack timeout after 10s
However, the second address corresponds to a server in the active site, rather than the passive.
The user did replication through gridSync from the active to the passive site and has some questions to be clarified as below.
Questions and Answers
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
Purpose |
Questions and Answers |
What these error messages mean and why they could be occurring? |
Why is it migrating the connections between nodes from the passive site to the active side? |
Does the replication process establish TMB connections between nodes from different sites for the transfer of data when replication is active? |
What exactly could it mean that these messages appear with certain frequency? Could it be related to poor performance on the cluster that connections are getting migrated? |
References |