question

Upvotes
Accepted
Akechi Sato avatar image
129 ●6 ●14 ●23

RFA C++ 100 milliseconds connection retry

The RFA log shows that RFA will be tried to recover the connection in 100 milliseconds.

[Fri May 1214:25:54 2017]: (ComponentName) Static: (Severity) Information:
RSSL_Cons_Connection  "Default::Connection_RSSL 192.168.27.46:14002"  will be tried in 100 milliseconds

However, in RFA configuration guide, the default value of connectRetryInterval is 1500 milliseconds. The application hasn’t set this value so the default value 1500 milliseconds should be used.

Why does RFA use 100 milliseconds instead of 1500 milliseconds?

treprfarfa-apiconnection
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 5.0 MiB each and 10.0 MiB total.

1 Answer

Upvotes
Accepted
Jirapongse avatar image
38.1k ●71 ●35 ●53

RFA uses 100 milliseconds reconnect timer when it fails over to another server defined in the serverList configuration. Currently, in RFA C++ 8.0.1, this value is un-configurable.

It will use the value in the connectRetryInterval when failing over to the first server in the serverList configuration. For example, if there are two servers in the serverList parameter and the connection to the SERVER_A is down, RFA will use 100 milliseconds reconnect timer to reconnect to SERVER_B.

\Connections\Connection_RSSL\serverList	= "SERVER_A, SERVER_B"

Then, if the connection to the SERVER_B is down, RFA will use the value of connectRetryInterval configuration as a reconnect timer to reconnect to SERVER_A which is the first server in the serverList parameter.

Therefore, if there is only one server in the serverList parameter, RFA will always use the value of connectRetryInterval as a reconnect timer.

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 5.0 MiB each and 10.0 MiB total.

Click below to post an Idea Post Idea