RTSDK JAVA EMA - login failed (timed out after waiting 45000 milliseconds) for :)

Vanessa Domo

Hi Team,

Can you please provide any insight into what might have caused the following?

2024-08-29 04:47:43,307+0000 ERROR [com.refinitiv.ema.access.OmmConsumerImpl] (main) [-] [] loggerMsg

ClientName: Consumer_RTO_1

Severity: Error

Text: login failed (timed out after waiting 45000 milliseconds) for

loggerMsgEnd

2024-08-29 04:47:43,310+0000 ERROR [com.refinitiv.ema.access.OmmConsumerImpl] (main) [-] [] loggerMsg

ClientName: ChannelCallbackClient

Severity: Error

Text: Received ChannelDown event on channel Channel_RTO

Instance Name Consumer_RTO_1

RsslReactor Channel is null

Error Id 0

Internal sysError 0

Error Location Reactor.processWorkerEvent

Error text Error initializing channel: errorId=-1 text=com.refinitiv.proxy.authentication.ProxyAuthenticatorImpl: Unexpected http response code: 403

loggerMsgEnd

The user just run 7 same Calypso scheduled tasks to get FX.USD.ZAR.TN quote. 6 of them completed successfully and just one failed (id 231508).

The user is using RTO v2 and confirmed not connecting through RTDS.

Thank you!

Kind regards,

Vanessa

Find more posts tagged with

java

rrto

ema-api

#technology

Accepted answers

Gurpreet

Hi @Vanessa Domo,

When multiple applications or multiple instances of same application use same credentials, every new instance invalidates the old token. So, this could be a case where instances were racing around to grab the access token from one another.

It is recommended that each application instance should have their own machine ID.

All comments

Gurpreet

Hi @Vanessa Domo,

It is recommended that each application instance should have their own machine ID.

EXPLORE OUR SITES