EMA TRCC disconnect handling
Hi,
I'm trying to understand how to handle disconnect/reconnect events in TRCC application. I have the following sequence of events and reaction of my application on them:
1. StatusMsg with state="Open / Suspect / None / 'channel down'" received on Login stream
2. StatusMsg with state="Open / Suspect / None / 'Channel is down.'" received on Login stream
3. StatusMsg with state="Closed, Recoverable / Suspect / None / 'Service for this item was lost.'" received on Tunnel stream
3. Application stops posting data
4. StatusMsg with state="Open / Ok / None / 'channel up'" received on Login stream
5. RefreshMsg with state="Open / Ok received on Login stream
5. Application sends and registers new Tunnel stream request
6. StatusMsg with state="Closed, Recoverable / Suspect / None / 'No matching service present.'" received on new Tunnel stream
7. Application is not connected and cannot post anything
So technically reconnection is successful on Login stream and API doesn't try to reconnect again. But tunnel stream is in "Closed, Recoverable" state and I cannot create new tunnel substream for data posting. What am I missing here? Should I unregister Tunnel stream and Tunnel substream upon receiving Open / Suspect on Login stream (although both these streams are closed as per EMA log...)?
Added EMA log: emalog.txt
Answers
-
Any thoughts on this? Maybe I received "Closed, Recoverable / Suspect" state on newly requested Tunnel stream because requested service was not up? Then what is recommended way to handle such case? I'm asking because it is not possible to reproduce this case on my side (it happened only once during 3 weeks of testing).
0 -
Ok, this is not some kind of special case. I tried to drop TCP connection with iptables and got exactly the same sequence of events:
1. Connection is down
2. Successful reconnect on Login stream with Refresh message
3. New Tunnel stream requested
4. "Closed, Recoverable / Suspect / None / 'No matching service present.'" state on newly created tunnel stream
I can restore connection only with full application restart, is it expected behavior?
0 -
Hello @Gurpreet.
ESDK 1.3.0 just release this month. Do you have a Jira ID for this bug so I can check if it was fixed yet?
0 -
Hi @Wasin Waeosri I dont have the JIRA ID, but this bug was not fixed in the latest release. TRCC development team provided an alternate mechanism to work around it for now.
EMA is responsible for sending a refresh message after a successful exchange of login and directory messages ( in that order ).
It turns out that EMA sends a refresh message too early even before directory message is exchanged on a network reconnection.0 -
Hello @Gurpreet
I have checked Jira ESDK-2715, the issue is not fixed in latest ESDK (1.5.1) yet. The development team seems to expect the fix in RTSDK 2.0.1 L1.
0 -
Thanks Wasin.
0 -
Update Sept 2020:
The bug is not fixed in the latest ESDK (1.5.1) yet. The development team expects it to be fixed in RTSDK 2.0.1 L1.
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 中文论坛