Socket exception when sending request.
Hi,
We are facing the following issue, after we have logged into the websocket and sending a request to get the RIC's we are using in the system.
The status we are receiving
{"ID":6,"Type":"Status","State":{"Stream":"Closed","Data":"Ok","Text":"Processed 209 total items from Batch Request. 209 Ok."}}
We have tried increasing the buffer size, but this does not seem to work.
Best Answer
-
Hello @charl.bester
Did you get any error messages or exceptions? Please be informed that the status close message with data state "Ok" and text "Processed <number> total items from Batch Request. <number> Ok." is an expected behavior when the application requests a batch request.
According to the WebSocket API - Batch tutorial page, when the application sends a batch request message to the server, the first thing we get back is a Status message confirmation of the Batch request:
Example confirmation message:
{
"ID":2,
"State":{
"Data":"Ok",
"Stream":"Closed",
"Text":"Processed 3 total items from Batch Request. 3 Ok."
},
"Type":"Status"
}The close status message above means the server is advising us that it has processed the Batch request and is now closing the request stream with ID of 2 – i.e. the Batch request Stream. This is because the server is going to create individual streams for each of the RICs and allocate a unique ID to each stream.
In your case, the WebSocket server should send the data of 209 items to the application after this close message.
Please see more detail on the WebSocket API - Make a Batch Request for Multiple Items Tutorial page.
2
Answers
-
Hi,
The actual exception that we are getting back is "Processed 209 total items from Batch Request. 209 Ok. "
0 -
As my colleague pointed out, this is a normal and expected response from the server, confirming that it has processed your batch request - as described in the above tutorial - Tutorials | Refinitiv Developers .
It is not an exception or error.
The message says 209 because I am guessing you sent 209 items in your batch request.
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 中文论坛