login failed while running the Consumer

Maha Rana Parthap Sing

Hi Team,

While running the consumer we are facing login failed issues. I would like to know why this is failing and how to resolve this. Could someone please help me on this?

2022-12-05 15:26:48.529 ERROR 21852 --- [           main] c.refinitiv.ema.access.OmmConsumerImpl   : 
loggerMsg
    ClientName: Consumer_1_1
    Severity: Error
    Text:    login failed (timed out after waiting 45000 milliseconds) for us-east-1-aws-3-med.optimized-pricing-api.refinitiv.net:14002)
loggerMsgEnd

2022-12-05 15:26:48.542 ERROR 21852 --- [           main] c.refinitiv.reps.ema.consumer.Consumer   :login failed (timed out after waiting 45000 milliseconds) for us-east-1-aws-3-med.optimized-pricing-api.refinitiv.net:14002)

wasin.w

Hello @Maha Rana Parthap Sing

I am sorry to hear that you are facing this connection issue.

The "login failed (timed out after waiting 45000 milliseconds) for <Hostname>:<Port>)" error message indicates that the API cannot connect to the RSSL <Hostname> server at <Port> within 45000 milliseconds. It does not relate to the invalid RIC request (the application gets "The record could not be found" in that case).

I am noticed the "http://" in the "login failed (timed out after waiting 45000 milliseconds) for http://us-east-1-aws-3-med.optimized-pricing-api.refinitiv.net:14002)" second log. Please be informed that you do not need to put "http://"or "https://&quot; to the DNS endpoint when connecting via the RSSL connection.

Please note that when the API connects to RTO (the us-east-1-aws-3-med.optimized-pricing-api.refinitiv.net of the US-EAST 1 zone in your case), the connection is via the public internet, so it may have latency, etc. You can adjust the amount of time (in milliseconds) the provider has to respond with a login refresh message before the API throws this exception via the Consumer's group LoginRequestTimeOut as follows:

My next point is you may try to connect to RTO endpoints in other regions (EU-WEST, AP-SOUTHEAST) that are closer to your application Region instead. You can set the preferred location via the API Service Discovery feature.

Example via EmaConfig.xml of the Consumer ex113_MP_SessionMgmt example:

<Channel>
    <Name value="Channel_4"/>
    <ChannelType value="ChannelType::RSSL_ENCRYPTED"/>
    <CompressionType value="CompressionType::None"/>
    <GuaranteedOutputBuffers value="5000"/>
    <!-- EMA discovers a host and a port from RDP service discovery for the specified location when both of them are not set and the session management is enable. -->
        
    <Location value="ap-southeast-1"/>
    <EnableSessionManagement value="1"/>
    <ObjectName value=""/>
</Channel>

Or check the onSuccess() method of the Consumer ex450_MP_QueryServiceDiscovery example to see how to query the preferred location manually.

### Is there a limit to how many existing connections are allowed for a user? ###

I highly recommend you reach out to your Refinitiv representative to get multiple Machine-IDs if you want to run multiple applications/sessions. If you use a single Machine ID with multiple sessions, the applications may encounter an error when an access token expires or when the applications attempt to refresh an access token.

### Is it ok to use the example EmaConfig.xml? This may contain all configurations. ###

Please note that the example EmaConfig.xml aims for demonstration purposes only. You may need to adjust or add additional parameters to match your application requirements.

For the RTO RSSL connection, you may check the Channel_4 configuration of the ex113_MP_SessionMgmt example.

Hopes this helps.