State: Closed/Suspect/Timeout - text: "Authentication token has expired."

Our application is connecting successfully, but the connection drops after a little while. It does so systematically when restarted.

The same code works fine for other instances using other machine IDs. I have verified that only this instance use the machineID and I was confirmed that it is dedicated.

Is there a configuration that would disable or interfere with the token refresh?

Here is the output in the log:

2023-02-23 06:18:03,692 ERROR [pool-5-thread-1] | com.refinitiv.ema.access.OmmConsumerImpl | | loggerMsg

ClientName: LoginCallbackClient

Severity: Error

Text: RDMLogin stream was closed with status message

username **********************************************************

usernameType 1

State: Closed/Suspect/Timeout - text: "Authentication token has expired."

loggerMsgEnd

2023-02-23 06:18:03,692 WARN [pool-5-thread-1] | com.zerobase.reuters.MonitorConsumerClient | | received status message on monitor: StatusMsg

streamId="1"

domain="Login Domain"

state="Closed / Suspect / Timeout / 'Authentication token has expired.'"

name="**********************************************************"

nameType="1"

StatusMsgEnd

Find more posts tagged with

token

session

ema-api

#technology

Accepted answers

Gurpreet

Hi @andre.malenfant,

Which version and language of SDK are you using?

There are couple of things you could try/verify:

Have you enabled the session management for this instance? It might be specified in the EMA config file or in your code.
Do other machine ID's successfully work on this instance of the code?
Do you still have this issue when using this machine ID with example code provided with the SDK?
You can also enable the XML log trace from the SDK to see whats happening on the streaming connection.

Since the token access/refresh endpoint is different from the streaming endpoint, is it possible that your firewall or other network component interfere with it. You can also play around with the token reissue ratio configuration paramete and reduce it to 0.5, see if that makes a difference.

All comments

Gurpreet

Hi @andre.malenfant,

Which version and language of SDK are you using?

There are couple of things you could try/verify:

Have you enabled the session management for this instance? It might be specified in the EMA config file or in your code.
Do other machine ID's successfully work on this instance of the code?
Do you still have this issue when using this machine ID with example code provided with the SDK?
You can also enable the XML log trace from the SDK to see whats happening on the streaming connection.

andre.malenfant

- Can you direct me to the session management configuration documentation?

-The same code works for other machine IDs

-I cannot test examples on this environment (prod)

-I have the trace enabled, maybe not all, will check that.

Gurpreet

Check the EMA Config guide. It is in the docs folder of the SDK. Here is the Java version of this guide - https://github.com/Refinitiv/Real-Time-SDK/tree/master/Java/Ema/Docs

EXPLORE OUR SITES