SDK not probing all IP adresses?

Hello,

A customer of ours reported an issue when the first of the four IP adresses specified in the connection string to FPPool_Open() became unavailable for some reason. The customer claims the other three addresses were still available but despite that, the call to FPPool_Open() failed with the following error information returned from the SDK ( and below are placeholders. Actual names were used in the connection string):

ECode = -10020, SysECode = 0, EClass = 1, Msg = no primary cluster found, EStr = FP_NO_POOL_ERR, Trace = ClusterCloud::getPrimaryCluster(0) \ \pea_file.PEA)<_FPPool_Open(192.168.122.146,192.168.122.147,192.168.122.148,192.168.122.149?\\ \ \pea_file.PEA) \ \pea_file.PEA)

The application log also shows that the "open" calls only took about 6-7 seconds to error out, whereas SDK documentation says the retry period for a non-responding IP address is one minute.

Only FP_OPTION_OPENSTRATEGY=FP_LAZY_OPEN option was set, no other global options used. The SDK version is 3.2.607

Why did the FPPool_Open() call fail when 3 of the 4 addresses were still available? Why did it take only few seconds to fail instead of 60 seconds? Is this a bug or expected behavior with FP_LAZY_OPEN strategy? Will switching to FP_NORMAL_OPEN strategy make the SDK actually probe all specified addresses if the firts IP address fails to respond?

Thank you,

Albert Pomortsev

Principal Software Engineer,

Global360, Inc.