Hi,
In OmmConsumerClient , what is the callback under which disconnection from ADS can be identified.
In onStatusMsg , onUpdateMsg , onRefreshMsg , this event is not captured.
Hi,
In OmmConsumerClient , what is the callback under which disconnection from ADS can be identified.
In onStatusMsg , onUpdateMsg , onRefreshMsg , this event is not captured.
Thank you for your participation in the forum.
Are any of the replies below satisfactory in resolving your query?
If yes please click the 'Accept' text next to the most appropriate reply. This will guide all community members who have a similar question.
Otherwise please post again offering further insight into your question.
Thanks,
AHS
Please be informed that a reply has been verified as correct in answering the question, and has been marked as such.
Thanks,
AHS
Hi @yajnasteju
EMA internally handles connection events, but doesn't forward them to the client application.
However, you can indirectly monitor connection activities through the login stream.
UInt64 loginHandle = consumer.registerClient( ReqMsg().domainType( MMT_LOGIN ).name( "user" ), client, closure );
Application will receive channel down status (via onStatusMsg) from login stream when there is a disconnection.
I have logged each message under status message , but Disconnection to ADS is not logged , but , few messages such as - 'Service to the item was lost ' are logged for individual ric codes.
Have you registered for login stream yet?
If you do, then there should be channel down events when there is a disconnection.
StatusMsg streamId="1" domain="Login Domain" ClearCache state="Open / Suspect / None / 'channel down'" name="u0160375" nameType="1" StatusMsgEnd StatusMsg streamId="1" domain="Login Domain" state="Open / Suspect / None / 'Channel is down.'" StatusMsgEnd
Note that the status is on "Login Domain". They will show up only when you register for login domain events.