EMA login failed

Hi Team, raising this case on behalf of a client.

Client is using RTO (EMA JAVA SDK). The client's production environment cannot log in and shows the following error message: login failed (timed out after waiting 45000 milliseconds) for http://ap-northeast-1-aws-1-sm.optimized-pricing-api.refinitiv.net:443). The client has been connected normally without any issues since December 23, 2025, but starting around 4AM Beijing time today, they were unable to log in. Could you please help check the reason?

Client's info as below:
clientId: GE-D5IJ2WXWJZ3U
How to connect to the service: EMA's JAVA SDK
Application log: Time zone: GMT+8 14:18

login failed (timed out after waiting 45000 milliseconds) for http://ap-northeast-1-aws-1-sm.optimized-pricing-api.refinitiv.net:443)

!-- Outgoing Reactor message -->

</elementList>

</attrib>

</key>

</dataBody>

</REQUEST>

2026-02-26 14:16:45.518 WARN c.r.ema.access.OmmConsumerImpl - loggerMsg

ClientName: ChannelCallbackClient

Severity: Warning

Text: Received ChannelDownReconnecting event on channel Channel_1

RsslReactor @4e7ff37a

RsslChannel @d710d0a

Error Id 0

Internal sysError 0

Error Location null

Error text Tunnel Channel Closed

loggerMsgEnd

2026-02-26 14:16:45.549 ERROR c.r.ema.access.OmmConsumerImpl - loggerMsg

ClientName: Consumer_1_2

Severity: Error

Text: login failed (timed out after waiting 45000 milliseconds) for http://ap-northeast-1-aws-1-sm.optimized-pricing-api.refinitiv.net:443)

loggerMsgEnd

Additional log information:

login failed (timed out after waiting 45000 milliseconds) for http://ap-northeast-1-aws-1-sm.optimized-pricing-api.refinitiv.net:443)

com.refinitiv.ema.access.OmmInvalidUsageExceptionImpl: login failed (timed out after waiting 45000 milliseconds) for http://ap-northeast-1-aws-1-sm.optimized-pricing-api.refinitiv.net:443)

at com.refinitiv.ema.access.OmmBaseImpl.ommIUExcept(OmmBaseImpl.java:2207)

at com.refinitiv.ema.access.OmmBaseImpl.handleLoginReqTimeout(OmmBaseImpl.java:1994)

at com.refinitiv.ema.access.OmmConsumerImpl.handleAdminDomains(OmmConsumerImpl.java:678)

at com.refinitiv.ema.access.OmmBaseImpl.initialize(OmmBaseImpl.java:373)

at com.refinitiv.ema.access.OmmConsumerImpl.<init>(http://OmmConsumerImpl.java:50)

at com.refinitiv.ema.access.EmaFactory.createOmmConsumer(EmaFactory.java:308)

at com.hexin.ifind.bond.reuters.data.main.consumer.ReutersChainCodeConsumer.run(ReutersChainCodeConsumer.java:46)

at com.hexin.ifind.bond.reuters.data.main.task.ReutersDataMonitorTask.lambda$checkReutersAllRicsSet$1(ReutersDataMonitorTask.java:163)

at java.base/java.lang.Thread.run(Thread.java:833)

2026-02-26 14:24:45.496 ERROR c.r.ema.access.OmmConsumerImpl - loggerMsg

ClientName: Consumer_1_24

Severity: Error

Text: login failed (timed out after waiting 45000 milliseconds) for http://ap-northeast-1-aws-1-sm.optimized-pricing-api.refinitiv.net:443)

loggerMsgEnd

Find more posts tagged with

java

refinitiv-realtime-optimised

#technology

RTO

Accepted answers

Jirapongse

@SylviaWu

Thank you for reaching out to us.

It is quite strange. The RTO supports both the Socket (14002) and WebSocket (443). The TCP port for the socket connection is 14002 and the TCP port for the WebSocket connection is 443.

Typically, when using the WebSocket connection, the outgoing message should be in JSON format.

<!-- Outgoing Reactor message -->

<!-- java.nio.channels.SocketChannel[connected local=/192.168.50.226:63669 remote=us-east-1-aws-3-sm.optimized-pricing-api.refinitiv.net/100.64.1.26:443] -->

<!-- Thu Feb 26 17:33:11 ICT 2026 -->

{"ID":1,"Type":"Request","Domain":"Login","KeyInUpdates":false,"Key":{"NameType":"AuthnToken","Elements":{"ApplicationId":"256","ApplicationName":"ema","Position":"192.168.50.226/PPC-D-BSPZ6S3","AuthenticationToken":"xtsa2QMh80snoslInvJKy0zpCuhZ","Role":0}}}

When using the Socket connection, the outgoing message should be in XML format.

<!-- Outgoing Reactor message -->

<!-- java.nio.channels.SocketChannel[connected local=/192.168.50.226:65173 remote=us-east-1-aws-3-sm.optimized-pricing-api.refinitiv.net/100.64.1.26:14002] -->

<!-- Thu Feb 26 17:30:59 ICT 2026 -->


<!-- rwfMajorVer="14" rwfMinorVer="1" -->

<REQUEST domainType="LOGIN" streamId="1" containerType="NO_DATA" flags="0x04 (STREAMING)" dataSize="0">

    <key flags="0x26 (HAS_NAME|HAS_NAME_TYPE|HAS_ATTRIB)" name="

Please confirm the version of EMA that the client is using and share the EMA configuration file used by the application.

All comments

Jirapongse

@SylviaWu

Thank you for reaching out to us.

It is quite strange. The RTO supports both the Socket (14002) and WebSocket (443). The TCP port for the socket connection is 14002 and the TCP port for the WebSocket connection is 443.

Typically, when using the WebSocket connection, the outgoing message should be in JSON format.

<!-- Outgoing Reactor message -->

<!-- java.nio.channels.SocketChannel[connected local=/192.168.50.226:63669 remote=us-east-1-aws-3-sm.optimized-pricing-api.refinitiv.net/100.64.1.26:443] -->

<!-- Thu Feb 26 17:33:11 ICT 2026 -->

{"ID":1,"Type":"Request","Domain":"Login","KeyInUpdates":false,"Key":{"NameType":"AuthnToken","Elements":{"ApplicationId":"256","ApplicationName":"ema","Position":"192.168.50.226/PPC-D-BSPZ6S3","AuthenticationToken":"xtsa2QMh80snoslInvJKy0zpCuhZ","Role":0}}}

When using the Socket connection, the outgoing message should be in XML format.

<!-- Outgoing Reactor message -->

<!-- java.nio.channels.SocketChannel[connected local=/192.168.50.226:65173 remote=us-east-1-aws-3-sm.optimized-pricing-api.refinitiv.net/100.64.1.26:14002] -->

<!-- Thu Feb 26 17:30:59 ICT 2026 -->


<!-- rwfMajorVer="14" rwfMinorVer="1" -->

<REQUEST domainType="LOGIN" streamId="1" containerType="NO_DATA" flags="0x04 (STREAMING)" dataSize="0">

    <key flags="0x26 (HAS_NAME|HAS_NAME_TYPE|HAS_ATTRIB)" name="

Please confirm the version of EMA that the client is using and share the EMA configuration file used by the application.

SylviaWu

Thank you for the response. It was helpful.

wasin.w V3

Hello @SylviaWu

Please ask the client to try the ex451_MP_OAuth2Callback_V2 example.

If the client wants to connect using the RSSL connection (socket), which is always a recommended connection type.

-clientId {client-id} -clientSecret {client-secret} -h ap-northeast-1-aws-1-sm.optimized-pricing-api.refinitiv.net -p 14002 -itemName {RIC}

If the client wants to connect using the WebSocket connection.

-clientId {client-id} -clientSecret {client-secret} -h ap-northeast-1-aws-1-sm.optimized-pricing-api.refinitiv.net -p 443  -websocket -itemName {RIC}

When using the WebSocket connection, the client needs to change the following code to match the dictionary file's location on the client's environment.

static void createProgramaticConfig(Map configDb) {
   …
   if(connectWebSocket){


	innerElementList.add( EmaFactory.createElementEntry().ascii( "DictionaryType", "DictionaryType::FileDictionary" ));
innerElementList.add( EmaFactory.createElementEntry().ascii( "RdmFieldDictionaryFileName", "./etc/RDMFieldDictionary" ));

	innerElementList.add( EmaFactory.createElementEntry().ascii( "EnumTypeDefFileName", "./etc/enumtype.def" ));

	elementMap.add( EmaFactory.createMapEntry().keyAscii( "Dictionary_1", MapEntry.MapAction.ADD, innerElementList ));

	innerElementList.clear();


	elementList.add( EmaFactory.createElementEntry().map( "DictionaryList", elementMap ));

	elementMap.clear();


	configDb.add( EmaFactory.createMapEntry().keyAscii( "DictionaryGroup", MapEntry.MapAction.ADD, elementList ));

	elementList.clear();

}
}

EXPLORE OUR SITES