Force Logout from DACS reasoning needed
See below logs, and client would like to speak to a dev on why this is happening
@timestamp,@message
2022-07-23 05:14:28.362,"<ads-fanout-med-az1-use1-prd.1.ads: Info: Sat Jul 23 05:14:26.885881 2022>
RSSL login close for ""GE-3785"" at position ""127.0.0.1/ld4macp1p1co1"" on host ""ld4macp1p1co1"" using application ""256"" of version ""etaj3.6.1.L1.all.rrg|emaj3.6.1.L1.all.rrg"" on channel 70.
Reason: Force Logout from DACS.
<END>
@timestamp,@message
2022-05-28 02:03:16.248,"<ads-fanout-med-az2-use1-prd.1.ads: Info: Sat May 28 02:03:16.058395 2022>
RSSL login close for ""GE-3785"" at position ""127.0.0.1/ld4macp1p1co1"" on host ""ld4macp1p1co1"" using application ""256"" of version ""etaj3.6.1.L1.all.rrg|emaj3.6.1.L1.all.rrg"" on channel 66.
Reason: Force Logout from DACS.
<END>
@timestamp,@message
2022-01-09 02:09:24.214,"<ads-fanout-med-az2-use1-prd.1.ads: Info: Sun Jan 09 02:09:21.928555 2022>
RSSL login close for ""GE-3785"" at position ""127.0.0.1/ld4macp1p1co1"" on host ""ld4macp1p1co1"" using application ""256"" of version ""etaj3.6.1.L1.all.rrg|emaj3.6.1.L1.all.rrg"" on channel 55.
Reason: Force Logout from DACS.
<END>
Best Answer
-
Hello @Spencer.Dixon ,
"Force logout from DACS" is not expected to happen often, but it is important, because it results in a disconnect.
A developer will not be able to confirm why the specific disconnect has taken place. It can be a server side or a connectivity issue:
- If the infra is provided by Refinitiv, such as Refinitiv Real-time Optimized, or Realtime hosted,
- The first place to check is Service Alerts on My Refinitiv -> Historical Alerts Search, select Status=All, to make to see any alerts that have been resolved by then.
- If the common cause is not found, one can open a support case to investigate the individual cause.
- If the infra is deployed and maintained locally, then the local market dat group/admin and the local network team should be the best point of contact to determine the specific cause.
A production-strength integration with a Real-time service should include the provision for detecting and handling of an occasional infra connectivity loss for any reason, including "Force logout from DACS". Please see this previous discussion thread with answers on how to detect and to handle.
Hope that this information helps
1 - If the infra is provided by Refinitiv, such as Refinitiv Real-time Optimized, or Realtime hosted,
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 中文论坛