I am establishing a connection to our ADS instance, but after I receive the successful login response, the logs only show connection ping timeouts.
If we look in our ADS, we notice that our application is connected, but the ADS does not receive any ping messages, so it will kill the connection after a while.
Our application in turn will then reconnect again, but the connection does not last again, so we are somewhat stuck in a loop.
I would expect the SDK to take care of the ping messages by itself, specially since there is nothing about them in the tutorials.
Does anyone know what we are doing wrong?
Basically, the Ping is used for detecting the state of the connection between the API and ADS server. When both sides are connecting, they will send pings to each other, and waiting for ping reply. If there is no problem between them, the sending side will expect the ping reply from the receiving side within the ping timeout value. If the ping reply does not come from receiving side within ping timeout value, it is interpreted as problem at the receiving side, and the connection is dropped.
The RFA API manages the Ping mechanism for the application. A ping-timeout problem could be caused by a network problem (between the API and ADS) or the application was run out of CPU time due to heavy load on the machine or the RFA thread exits abnormally or blocked.
To let us verify this issue in detail, please give us the following information
You can configure the following RFA Java configurations to enable the log file
<node name="rsslConnection"> <map> <entry key="connectionType" value="RSSL"/> <entry key="serverList" value="ad"/> <entry key="portNumber" value="14002"/> <entry key="ipcTraceFlags" value="7"/> <entry key="mountTrace " value="True"/> <entry key="logFileName" value=".\logs\RSSL_%U.log"/> <entry key="traceMsgDomains" value="ALL"/> </map> </node>