EMA (OnInvalidUsage callback function) - Error text: login failed (timed out after waiting 45000 mil

Question

Our client developer is working on EMA adapter to subscribe to streaming data via RTMDS.  They have shared the configuration details below. Their adapter is based on C#.Net using EMA sdk library.

However, they are unable to connect and are getting following message: EMA (OnInvalidUsage callback function) - Error text: login failed (timed out after waiting 45000 milliseconds) for ads-host:14002, Error code:-4052

They are able to telnet to ADS on port 14002 and DACS id is valid but repeatedly getting below error. What could be the reason.

Note from developer:

As requested , We are using connection details as per below.

Kindly note that FinIQ RMDS adaptor is based on C#.Net using EMA sdk library.

Host : 159.43.84.35

Port : 14002

DACS: MB1_02_HFMA_IN47433_003

Service name : “hEDD”

RIC : “EUR=”

Service name = “hEDD”

RIC: “INR=”

Service name = “hEDD”

RIC: “JPY=”

—————————————————————-

The log file details with error login failed for reference.

info: FinIQ.Services.FXSpotReutersEMA.Workers.EmaWorker[0]

Starting EMA consumer...

info: Microsoft.Hosting.Lifetime[14]

Now listening on: http://0.0.0.0:8080

info: Microsoft.Hosting.Lifetime[0]

Application started. Press Ctrl+C to shut down.

info: Microsoft.Hosting.Lifetime[0]

Hosting environment: Development

info: Microsoft.Hosting.Lifetime[0]

Content root path: /app

fail: FinIQ.Services.FXSpotReutersEMA.EMA.EmaErrorClient[0]

EMA (OnInvalidUsage callback function) - Error text: login failed (timed out after waiting 45000 milliseconds) for ads-host:14002, Error code:-4052

info: FinIQ.Services.FXSpotReutersEMA.Workers.EmaWorker[0]

EMA connected successfully.

warn: FinIQ.Services.FXSpotReutersEMA.Workers.EmaWorker[0]

No data received recently. Reconnecting...

info: FinIQ.Services.FXSpotReutersEMA.Workers.EmaWorker[0]

Cleaning up EMA consumer...

Jirapongse · Answer

@MayurC

At the end of the log file, the application can retrieve data properly.

info: FinIQ.Services.FXSpotReutersEMA.Workers.EmaWorker[0]

      Starting EMA consumer...

dbug: Microsoft.Extensions.Http.DefaultHttpClientFactory[100]

      Starting HttpMessageHandler cleanup cycle with 1 items

dbug: Microsoft.Extensions.Http.DefaultHttpClientFactory[101]

      Ending HttpMessageHandler cleanup cycle after 0.0029ms - processed: 0 items - remaining: 1 items
dbug: FinIQ.Services.FXSpotReutersEMA.EMA.FXAppClient[0]

QoS: RealTime/TickByTick
dbug: FinIQ.Services.FXSpotReutersEMA.EMA.FXAppClient[0]

RIC = EUR=, BID = 1.1633, ASK = 1.1634

info: FinIQ.Services.FXSpotReutersEMA.Workers.EmaWorker[0]

      EMA connected successfully.

dbug: FinIQ.Services.FXSpotReutersEMA.EMA.FXAppClient[0]

      STATUS: Open / Suspect / None / 'Service not available'
dbug: FinIQ.Services.FXSpotReutersEMA.EMA.FXAppClient[0]

QoS: RealTime/TickByTick

dbug: FinIQ.Services.FXSpotReutersEMA.EMA.FXAppClient[0]

RIC = INR=, BID = 96.305, ASK = 96.315

DB: INR= 96.305/96.315

DB: EUR= 1.1633/1.1634

dbug: FinIQ.Services.FXSpotReutersEMA.EMA.FXAppClient[0]

RIC = EUR=, BID = 1.1632, ASK = 1.1634

The error has been changed. Now it is the 'Service not available' message which indicates that the subscribed service is not available on the connection.

The client can test the connection by running the example application in the RTSDK package and enable the trace log in the library to verify what the problem is. To enable the EMA Java logging, please refer to this Learn how to direct EMA Java log to Java Logging API article.

MayurC · Answer

@Jirapongse,

159.43.84.35 is the ADS server and is reachable via telnet from the same server. they have tre using IP as well. result being same.

response from client dev: and Logs attached.

retema-7454dbfdcf-p29gs-retema (1).log

As discussed with our Dev team, we are not using EmaConfig.xml file in our deployment.

We have an application-specific configuration file, as shown below, which contains the necessary configuration used by the RMDS adaptor at runtime to overwrite the default values for OmmConsumerConfig.Host. I will check if any other trace log files are getting generated in environment and share with you today.

{

"Logging": {

"LogLevel": {

"Default": "Information",

"Microsoft.Hosting.Lifetime": "Information"

}

},

"Ema": {

"ConsumerConfig": {

"Host": "159.43.84.35",

"Port": 14002,

"UserName": "MB1_02_HFMA_IN47433_003 "

},

"StaleSeconds": 30,

"Pipeline": {

"ChannelCapacity": 1000

},

"PublishAPIEndPoint": ""

},

"TestData": {

"SubjectFeedMap": [

{

"Service": "hEDD",

"RIC": "EUR="

},

{

"Service": "hEDD",

"RIC": "INR="

},

{

"Service": "hEDD",

"RIC": "JPY="

}

]

}

Jirapongse · Answer

@MayurC

Thank you for reaching out to us.

Typically, this error indicates that the library couldn't establish a connection to the server. In this case, the server is ads-host:14002.

EMA (OnInvalidUsage callback function) - Error text: login failed (timed out after waiting 45000 milliseconds) for ads-host:14002, Error code:-4052

However, according to the information, the server is 159.43.84.35.

Could you confirm whether ads-host and 159.43.84.35 refer to the same server? The client can use the IP address (159.43.84.35) in place of the server name.

EXPLORE OUR SITES