RTO - 'Force Logout from DACS' in the EMA 'login domain' message.

Frederic

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

wasin.w

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.

Frederic

https://community.developers.refinitiv.com/discussion/comment/87319#Comment_87319

wasin.w

Nov 16, 2021

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.

Can the EMA ErrorClient or StatusMsg handler capture this kind of issue?

umer.nalla

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); 

umer.nalla

Hi @zoya faberov

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

Frederic

https://community.developers.refinitiv.com/discussion/comment/87332#Comment_87332

Many thanks @umer.nalla for the information.