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.

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

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