Why am I receiving a "JSON parser error" message from Elektron WebSocket?

I am receiving this error message about once per minute:
[{"ID":0,"Type":"Error","Text":"JSON parser error: -3","Debug":{"File":"Converter/jsonToRwfBase.C","Line":462,"Message":"08/16/2018 12:42:20"}}]
The only other messages I'm sending around this time is {"Type":"Ping"}, for which I receive a Pong,
or my response to the servers Ping, for which i send {"Type":"Pong"}.
Thanks in advance for any helpful ideas.
Best Answer
-
Finally discovered the source of the issue - I was using Websocket4net library https://github.com/kerryjiang/WebSocket4Net, and it's default configuration is to send a ping with timestamp every 60 seconds. If you are using this library, set EnableAutoSendPing to false.
0
Answers
-
Can you please provide additional details like RIC and language and particular example used when you get this error.
If connecting to a local TREP, we will need the ADS version as well.
0 -
@james_molohon,
Ensure you are sending a full and valid message. For example, a message like:{"Type":"Ping"
would produce this error since the closing bracket is missing.
0 -
We are running version 2.6 on ADS. Our language is C#, and is similar to the sample code. Sorry ,but I am unable to share my code. I'm logging all messages sent and received. I see expected responses for the messages I send, but not sure why I continue to see this parser error with ID:0 at a one minute interval on every application that we use to connect to the websocket.
0 -
I see that the error's Message field shows that the ADS appears to have received a frame containing only a date & time:
08/16/2018 12:42:20
Looks like that was the current date & time. Is your application sending that over the WebSocket?
0 -
I have a method that logs every message before sending over the websocket, and I don't see anything logged that resembles just the date and time. I have observed that we only receive the parser error message during periods when we are sending ping messages to keep the connection open, and not when we are fetching prices. But still I see the pings and pongs as noted in the original post, and the expected response from the websocket.
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
- 685 Datastream
- 1.4K DSS
- 615 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 252 ETA
- 556 WebSocket API
- 38 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 652 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
- 104 UPA
- 193 TREP Infrastructure
- 228 TRKD
- 917 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛