We had built the example Consumer113 from EMA C++ documentation into a remote server, but run into error as below:
Exception Type='OmmInvalidUsageException', Text='Failed to add RsslChannel(s) to RsslReactor. Channel name(s) Channel_3
Instance Name Consumer_3_1
Error Id -1
Internal sysError 0
Error Location C:\Real-Time-SDK-master\Cpp-C\Eta\Impl\Reactor\rsslReactor.c:6892
Error Text Failed to request authentication token information. Text: <C:\Real-Time-SDK-master\Cpp-C\Eta\Impl\Reactor\Util\rsslRestClientImpl.c:1595> Error: Failed to perform the request with text: Timeout was reached', ErrorCode='-1'
- Channel_3 details:
<!-- EMA discovers a host and a port from EDP-RT service discovery for the specified location
when both of them are not set and the session management is enable. -->
<!-- ObjectName is optional: defaulted to "" -->
- Service name is ELEKTRON_DD
- We had set RequestTimeout to 5 minutes (300000 ms), under Consumer_3
- We are able to telnet both IP 188.8.131.52 and 184.108.40.206, paired with port 443 and 14002 from the server which this error happens.
- We also run the exact program in our local server which worked perfectly fine.
As we did not have access to check most of the settings in that server, we would like to know what can cause this error to happen, so that we can request those details from the server admin.
Thanks in advance.
Also, the service discovery will return endpoints list, which is dynamic and will depend on your login ID (tier) and your geographic region. A list of VPC privatelinks endpoints is provided in the Refinitiv Real-Time - Optimized Install and Config Guide document. For whitelisting public IP's please contact Refinitiv support to get a list of all the IP's.
Can you please confirm that you are using the latest version of the API. Also, that you have the credentials to access the Optimized service in the cloud and that you have created an appropriate appKey (aka clientID).
Are you implying that the Consumer113 sample is able to connect to cloud and get data from one machine and not another?
Hi @Gurpreet, thank you for your replies.
We contacted the client server admin and got an user ID that can access Resource Monitor. From TCP connection under Network tab, we found out that the program was sending bytes to awsglobalaccelerator, but not receiving any, thus resulting this time out issue. After turning off antivirus, the program run successfully.