Is there limitation on post msg size or field size using Websocket API?

I have created a record in ATS (RIC and field names masked:):
Description in ats.dico file
*SOME_RIC admin None AA DEFAULT DEFAULT DEFAULT RESET 08/12/2031 08/12/2021 NONE NONE
v STR_T SOME_RIC.FLD1 STATIC_CONTRIB[]
v STR_T SOME_RIC.FLD2 STATIC_CONTRIB[]
v STR_T SOME_RIC.FLD3 STATIC_CONTRIB[]
v STR_T SOME_RIC.GN_TXT32_3 STATIC_CONTRIB[]
v STR_T SOME_RIC.GUID STATIC_CONTRIB[]
There are custom fields used that are properly set RDMFieldDictionary (also masked for the purpose of this question):
FLD1 "FLD1" -4001 NULL ALPHANUMERIC 40000 RMTES_STRING 40000
FLD2 "FLD2" -4011 NULL ALPHANUMERIC 2000 RMTES_STRING 2000
FLD3 "FLD3" -4021 NULL ALPHANUMERIC 40000 RMTES_STRING 40000
I am using simple python code to contribute to that RIC via Websocket API.
It turns out that I cannot push more to FLD1 field than approx 1,5-2k of data while it should accept up to 40k as per definition.
It's worth noting that when I subscribe to similar RIC that already has longer strings in it (approx 25k) I can retrieve it properly thru the same code in python via Websocket API.
Please advise if there are any limitations to contribution via EWA?
Best Answer
-
The only limit I am aware of with the Websocket API is a total JSON message payload size of 64k per message. Is it possible the total message size is exceeding 64k?
Can you confirm what if any error message/response you get from the ADS or ATS when you submit the 40k field size?
There could also be other limits applied by RTDS or ATS that I am not aware of.
I would recommend you speak to your internal Market data team and ask them to examine their ATS and/or ADS/ADH logs to see if there are any further messages/errors. If they need help with this process, then they can raise a ticket for Refinitiv Real-Time Advanced Transformation Server or Advanced Distribution Server at My.Refinitiv so they can help diagnose where the issue may lie e.g. by checking logs etc on either of those products.
0
Answers
-
Hi
There are no errors in ATS logs nor ADS's. I can actually see contribution success. The size of JSON is also <64k. Since there are no limitations on EWA I will raise the ticket with support to see if my ats/rtds config is ok.
Thank you very much for your help.
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 690 Datastream
- 1.4K DSS
- 629 Eikon COM
- 5.2K Eikon Data APIs
- 11 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 255 ETA
- 559 WebSocket API
- 39 FX Venues
- 15 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 25 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 280 Open PermID
- 45 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 716 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 27 DACS Station
- 121 Open DACS
- 1.1K RFA
- 106 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 95 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛