Source has gone down status message followed by loss of connectivity

sgupta

We are subscribing to realtime updates using the EMA API on 2 servers.

We received the "A23: Source has gone down" status message followed by the "A24: Moving item to new server which has lower server id" status message on both the servers.

On one of the servers we received the channel-down message which we are handling to reconnect/resubscribe but the other server did not receive this and ended up not getting any updates. So the data on that server was stale.

Why did this happen? How do we avoid this going forward? Should we automatically reconnect if we receive the "Source has gone down..." or "Moving item to new server..." status messages?

moragodkrit.chumsri_1

@sgupta

-As far as I know, the message start with "A23:" and "A24:" generated by the TREP component such as ADS server. There might be an issue occurs on the infrastructure side and it may try to switch to the next server. I suggest you contact TREP support team to verify issue on the infrastructure side first and explain about the status text.

You can contact the team by submit case using Contact Us form.

Regarding to the application, not sure that

-What is item Stream State and Data state your application received after getting the message?

-Have you seen any error message in EMA Log or trace log?

Basically if the connection has gone down, API should automatically reconnect. And after it reconnected, the item status depending on the Item Stream state and Data state when the problem occurs. If the item stream state is closed/closerecover , your application has to re-request the item itself. But if the item stream state is open and data state is suspect, application should be able to receive update as usual.