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>

Find more posts tagged with

error

OMM

DACS

rrto

log-out

Accepted answers

zoya faberov

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

All comments

zoya faberov

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.

Hope that this information helps

EXPLORE OUR SITES