question

Upvotes
Accepted
5 0 1 3

“CLOSE_RECOVERY" Dead Loop

Our client side program has successfully connected with cloud TRCC.

During my re-connection testing, after some POST messages are sent out successfully to TRCC, I plug out the network cable and re-plug in 1 min later.

A status msg with state="Closed, Recoverable / Suspect / None / 'channel down.' is callback, and then EMA starts to re-connect and re-authenticate automatically.


However, from the trace log, the ‘TunnelStream Open request’ could NOT be seen. Just ‘Device Login request’ and ‘SOURCE request’ are sent out, and re-sent continuously in a constant interval.

So that causes there is NO chance to callback onStatusMsg() for client sending ‘TRCC AAA Login request’ out during re-connection, and program dead loop.


Question:

how to handle this scenario? or any code/function/callback missed in our program? (we already follow the example: https://developers.refinitiv.com/elektron/elektron-sdk-java/learning?content=41885&type=learning_material_item).

elektronrefinitiv-realtimeelektron-sdkrrtema-apielektron-message-api
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 5.0 MiB each and 10.0 MiB total.

1 Answer

Upvotes
Accepted
11.3k 25 8 13

Hi @wesley.zhang,

Once connection go down, the Tunnel Stream will be closed and there is no recovery on tunnel stream. Application has to create a new Tunnel Stream once the connection is recovered. You can find the instructions for EMA application to handle the tunnel stream recovery in this question.

To better understand the issue, could you provide the application trace log and some information on how your application handle the connection down?

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 5.0 MiB each and 10.0 MiB total.

Click below to post an Idea Post Idea