EMA Subscription of RIC failing

I am getting Channel Down event, althogh connecting using ReconnectAttemptLimit as -1.
state="Open / Suspect / None / 'channel down'"
After channel down, any subscription failed due to below error and unable to get the data. Do I need to reinitialize my subscription client :
DEBUG EmaConnection [RFA Dispatch Thread]: Data State : [Suspect], Stream State : [Open] , MDS Status response [Service not up]
Restart my application fixed this issue.
Is there any way to receive channel up event with any configurition?
Best Answer
-
Hello @vikas.chaudhary
The state="Open / Suspect / None / 'channel down'" message means the data stream is still opened, but the data is not available because the channel down event. Basically, once the connection is recovered and service is up, the API automatically recover subscription for the application.
However, the log "DEBUG EmaConnection [RFA Dispatch Thread]: Data State : [Suspect], Stream State : [Open] , MDS Status response [Service not up]" message indicates the Service is down (Are you using EMA or RFA?). The API may need time to wait for the upstream service to UP again.
For EMA you can register the following streams events for monitoring connection and service status health:
- Register the Login Stream for monitoring connectivity status: See Cons333 (C++) or ex333_Login_Streaming_DomainRep (Java)
- Register the Directory stream for monitoring the Service status: See Cons331 (C++) or ex331_Directory_streaming (Java)
Additionally, if you need a dedicated Real-Time APIs support ticket with SLA, I recommend you register to be RDC named user, then you can submit a ticket to the RDC support team via the "Contact premium support" button on the https://developers.refinitiv.com/en/api-catalog/refinitiv-real-time-opnsrc/rt-sdk-cc or https://developers.refinitiv.com/en/api-catalog/refinitiv-real-time-opnsrc/rt-sdk-java pages.
- Please contact your Refinitiv Representative or Account Manager to help you with the RDC subscription process.
0
Answers
-
Any update please. Thanks
0 -
Thanks,, I have raised this with Premium Support.
So my question is in which scenario application will not receive Channel Up event after Channel Down event.
0 -
Hello @vikas.chaudhary
If the Login state is "Open/Suspect", the API should try to reconnect until the channel up.
I recommend you contact the RDC support team to verify this behavior in detail.
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
- 684 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
- 249 ETA
- 554 WebSocket API
- 37 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
- 643 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
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 192 TREP Infrastructure
- 228 TRKD
- 915 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 中文论坛