Failed to perform the request with text: Timeout was reached
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
RsslReactor 0x00000157CD07F1E0
RsslChannel 0
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'
Some details:
- Channel_3 details:
<Channel>
<Name value="Channel_3"/>
<ChannelType value="ChannelType::RSSL_ENCRYPTED"/>
<CompressionType value="CompressionType::None"/>
<GuaranteedOutputBuffers value="5000"/>
<!-- 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. -->
<Location value="ap-southeast"/>
<EnableSessionManagement value="1"/>
<EncryptedProtocolType value="EncryptedProtocolType::RSSL_SOCKET"/>
<!-- ObjectName is optional: defaulted to "" -->
<ObjectName value=""/>
</Channel>
- Service name is ELEKTRON_DD
- We had set RequestTimeout to 5 minutes (300000 ms), under Consumer_3
- We are able to telnet both IP 52.76.141.204 and 54.151.172.199, 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.
Best Answer
-
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.
0
Answers
-
Hi @kiawaichia1995,
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?
0 -
- According to EmaVersion.h, the version of EMA we used is 3.5.1.L1.
- Yes we had the credentials needed (Username, Password, ClientID)
- Yes the sample is able to connect to cloud and get data from our local machine/server, but not the remote client server (both are Windows 2016 x64 Datacenter and located within SEA).
- Since we only had limited access to that server, we need to request for more information on why we cannot connect from there. To do that, we need your assistance to provide us the essential requirement (IE. IP address or ports )to connect to the server, for us to check if that server misses something.
So far, we found 3 IPs (75.2.0.254, 52.76.141.204, 54.151.172.199) and 2 ports (443 and 14002) are connected when the sample is running through debugging and Resource Monitor. All these IPs and Ports are telnet-able in the client server.
Any additional suggestions for us to test in the client server (IE. more IPs or Ports) is appreciated.
0 -
I am able to get similar error when I try to use the older version of EMA. Please download and install the latest version of SDK.
0 -
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.
0
Categories
- All Categories
- 6 AHS
- 37 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛