Encounter Text Message Encoding Failure on client side
We have tried to deploy the EMA C++ Provider/Consumer on some RHEL 8.7 servers, with EMA version 3.6.5, and we got the following error on client side:
loggerMsg
TimeStamp: 20:04:36.916
ClientName: ChannelCallbackClient
Severity: Success
Text: Received ChannelUp event on channel Channel_1
Instance Name Consumer_1_1
Connected component version: eta3.6.5.L1.rrg|ema3.6.5.L1.linux 64-bit Static(Optimized)
loggerMsgEnd
loggerMsg
TimeStamp: 20:04:36.916
ClientName: ChannelCallbackClient
Severity: Warning
Text: Received ChannelDownReconnecting event on channel Channel_1
Instance Name Consumer_1_1
RsslReactor 0x0x251a740
RsslChannel 0x0x251a740
Error Id -29
Internal sysError 0
Error Location /local/jenkins/workspace/ESDKCore_RCDEV/OS/OL7-64/rcdev/source/rtsdk/Cpp-C/Eta/Impl/Reactor/Watchlist/rsslWatchlistImpl.c:4863
Error Text Message encoding failure -- -29.
loggerMsgEnd
We have enabled the XML debug log on the EmaConfig file on the provider side, and it only shows the "closed channel".
We have done some investigations and we found that not all RHEL 8.7 server has the issues. During the investigation, we are using the same binaries/config/dictionary/enumDef, so the behavior is exposed to be consistent but it is not. Some servers are working properly and some of them are not.
Did anyone encounter this issue before?
Best Answer
-
Thanks for reaching out to us.
First of all, you may need to upgrade the application to use the latest version of RTSDK. The latest version is RTSDK C/CPP 2.1.1.L1 aka EMA/ETA 3.7.1.L1. You can download it from the Refinitiv Developer Portal or Software Downloads. The API is in the MDS - API product family
If the problem still happens with the latest version of the API. You may need to contact the API support team to investigate this issue.
According to the error code (-29), it is RSSL_RET_INVALID_DATA which indicates that invalid data was provided to the invoked function. You may need to verify how the application creates request messages.
0
Answers
-
Thank you for your suggestions.
Let us try to upgrade the SDK and test it again. We will get back to you later.
For the request messages creation logic, I think it should be correct as it does work in some servers for the same binaries of the application.
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 中文论坛