Java EMA - Library stopped reconnecting

Zeno

Hello all,

We are using the Java EMA library "group: "com.refinitiv.ema", name: "ema", version: "3.9.0.1", and we encountered the following case:

The library is set up to use HMDS websockets with protocal rssl.rwf, set up such that it can reconnect like so: APAC → AMERS → EMEA

We encountered a few disconnects and reconnects, but at one point we received the following series of events/logging messages:

1. 10:54:22,220 - Channel Up From Emea
2. 10:54:22,220 - High watermark on it
3. 10:54:22,644 - "Login Denied:Failed to lookup sso token"
4. 10:54:25,654 - ERROR: loggerMsg
   ClientName: <redacted>
   Severity: Error
   Text: Failed to uninitialize OmmBaseImpl (_executor.awaitTermination() timed out).
   loggerMsgEnd
5. 10:54:25,663 - ClientName: <redacted>
   Severity: Error
   Text: Failed to close reactor channel (rsslReactorChannel).' RsslChannel='0Error Id -10Internal sysError 0Error Location ReactorChannel.closeError Text Reactor is shutdown, close aborted.'.
   loggerMsgEnd
6. 10:54:25,665 - Missing, unreadable or empty file configuration <expected as we make the config programatically>
7. 10:54:25,665 - no configuration exists in the config file for consumer dictionary <expected as we make the config programatically>
8. 10:54:25,665 - no configuration exists in the config file for consumer dictionary <expected as we make the config programatically>
9. 10:54:26,931 - Channel UP for APAC
10. 10:54:26,931 - High water mark set on the channel
11. 10:55:12,982 - Received ChannelDownReconnecting event on APAC with "Error text Connection reset"
12. 10:55:12,982 - WARN: loggerMsg
    ClientName: LoginCallbackClient
    Severity: Warning
    Text: RDMLogin stream state was changed to suspect with status message
    username <not set>
    usernameType <not set>
    State: Open/Suspect/None - text: ""
    loggerMsgEnd
13. 10:55:12,983 - WARN: loggerMsg
    ClientName: ChannelDictionary
    Severity: Warning
    Text: RDMDictionary stream was closed with status message
    streamId 3
    Reason State: Closed, Recoverable/Suspect/None - text: "channel down."
    loggerMsgEnd
14. 10:55:12,985 WARN: loggerMsg
    ClientName: ChannelDictionary
    Severity: Warning
    Text: RDMDictionary stream was closed with status message
    streamId 4
    Reason State: Closed, Recoverable/Suspect/None - text: "channel down."
    loggerMsgEnd

And then it stops. It does not retry to recreate the connection. Usually it would reconnect automatically, or continue to try, as there was another successful reconnect 4 hours before this one that had the same 4 messages at the end (points 11, 12, 13, 14).

My question is if the errors from points 4 and 5 could lead to the library not remaking the connection or something related to that?

Please feel free to ask any questions.

Jirapongse

@Zeno

Thank you for reaching out to us.

According to the log, the application may create a new consumer at point 6. Yes, typically, the consumer should reconnect to the server. The latest version of Real-Time Java SDK is RTSDK Java 2.3.1.L1 aka EMA/ETA 3.9.1.L1 aka 3.9.1. You may try the latest one to avoid all known issue.

However, normally LSEG Developer Community Forum is for how-to/general questions but your question seems to be more complex and requires investigation e.g. review source code, configuration, try to reproduce the problem etc.

I recommend you raise a query through the premium support service. If you are a named user of that service you should see a link "Contact Premium Support" when you are logged into the product page.