RTO - 'Force Logout from DACS' in the EMA 'login domain' message.
The question is about the suggestion on how to recover the application in such case of failure?
Monitor which type of event and then going to re-create the consumer?
StatusMsg
streamId="1"
domain="Login Domain"
state="Closed / Suspect / Not entitled / 'Force Logout from DACS.'"
name="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" (please ignore this)
nameType="1"
StatusMsgEnd
Best Answer
-
Hello @Frederic
The status message "Closed / Suspect" on the Login stream indicates that the logins stream between the API and the server is closed. The closed login stream also closes all opened streams and the API will not recover the streams.
The application needs to re-create the OMMConsumer to re-open the login stream to reconnect to the server.
The 'Force Logout from DACS.' error message is generated from the server. If the client is connecting to the RTO, I highly recommend the client contact the RTO support team to verify the server-side.
0
Answers
-
0
-
Hi @Frederic
If the customer adds a registerClient for Login or specifies a callback client for OmmConsumer, then they should receive a StatusMsg for when the Login stream is closed.
e.g.
- example 333_Login_Streaming_DomainRep - where you explicitly registerClient for LOGIN
- or example 330_Login_Streaming - where you specify the AppClient to receive callback events when creating the OmmConsumer
// Example 333
UInt64 loginHandle = consumer.registerClient( Login::LoginReq().name( "user" ).getMessage(), client, closure );
OR
// Example 330
OmmConsumer consumer( OmmConsumerConfig().operationModel( OmmConsumerConfig::UserDispatchEnum ).username( "user" ), client);0 -
On a Force Logout from Dacs where the Login Stream is closed, you would need to delete the OmmConsumer and create again to initiate a new connection + login etc
0 -
@umer.nalla for the information.Many thanks0
Categories
- All Categories
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 33 Data Model Discovery
- 682 Datastream
- 1.4K DSS
- 613 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
- 248 ETA
- 552 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.8K Refinitiv Data Platform
- 622 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
- 191 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 84 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛