MarketPrice domain connection loss

@Ron Bove
At 04:49UTC on 27th January, we received a status message with no state on all the connections using the uat_puffin login:
StatusMsg
streamId="1697"
domain="MarketPrice Domain"
itemGroup="00 f8"
name="STXE43000D4.EX"
nameType="1"
serviceId="259"
serviceName="hEDD"
StatusMsgEnd
I think the RIC is irrelevant, because it happened at exactly the same time on all connections, with different RICs.
It feels that the connection has died, because at the moment, we are responding to messages like this by uninitializing the OmmConsumer and creating a new one to reconnect, but we fail on the first step with this error:
OmmConsumerImpl loggerMsg
ClientName: EmaConsumer_2
Severity: Error
Text: Failed to uninitialize OmmBaseImpl (_executor.awaitTermination() timed out).
loggerMsgEnd
This is leaving us stuck until we manually do a complete restart of our application.
Are you able to give any advice on what the status message represents? And why we are unable to uninitialize the consumer?
Best Answer
-
You haven't captured enough information in the status message. If your application is able to reproduce this error, then please turn on the OMM logs from SDK which should contain the reason and the ststus code.
If the connection had failed, then once it resumes, the OMMConsumer automatically re-connects. The SDK takes care of re-subscribing to all the open items on applications behalf. Since your application is connecting to local market data system, you can probably see the reason for this status/connection loss in the ADS logs as well.
0
Answers
-
Hello @malcolm.cudworth
About how to turn on the OMM logs, please see the "Logger Configuration" section of the Enterprise Message API (EMA) - Configuration Overview article.
0 -
Typically, a status message can convey changes in:
- stream state or data state
- stream's permisioning information
- item group
According to your information (a status message with no state), a status messgae may convey changes in an item group. However, it is better to contact the server team to confirm this.
Regarding the error message, I checked the code on GitHub and found that the API will report this error if it can't shutdown the executor within the SHUTDOWN_TIMEOUT_IN_SECONDS (3 seconds). I assume that the API may be still dispatching messages to the applicaiton.
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
- 616 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
- 557 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
- 653 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
- 229 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 中文论坛