question

Upvotes
Accepted
1 0 0 2

TREP API connectivity failover issues

Hi Developer Support,

We are observing some failover issues with our processes connecting to the TREP edge servers via the Refinitiv APIs.

In this instance, we notice the API repeatedly tries to login to another channel but kept failing.

Channel 1 and 3 are configured to the same TREP server IP and port but the connection has been refused.

Please see the log snippets below:

2020-03-18 10:47:18.869 INFO [pool-2-thread-1] OmmConsumerImpl - loggerMsg

ClientName: ChannelCallbackClient

Severity: Info

Text: Received ChannelUp event on channel Channel_3

Instance Name Consumer_1_1

Component Version ads3.3.1.L1.linux.tis.rrg 64-bit

loggerMsgEnd

2020-03-18 10:47:33.904 WARN [pool-2-thread-1] OmmConsumerImpl - loggerMsg

ClientName: LoginCallbackClient

Severity: Warning

Text: RDMLogin stream state was changed to suspect with status message

username <not set>

usernameType <not set>

State: Open/Suspect/None - text: ""

loggerMsgEnd

2020-03-18 10:47:33.904 INFO [pool-2-thread-1] RTROmmConsumer - [registerClient] Item: <not set> / Service: <not set> [State: Open / Suspect / None / '']

2020-03-18 10:47:36.744 INFO [Thread-7] SL_SubMgr - proUnsub starting check

2020-03-18 10:47:36.744 INFO [Thread-7] SL_SubMgr - proUnsub check end. Count=1

2020-03-18 10:47:48.933 WARN [pool-2-thread-1] OmmConsumerImpl - loggerMsg

ClientName: LoginCallbackClient

Severity: Warning

Text: RDMLogin stream state was changed to suspect with status message

username <not set>

usernameType <not set>

We decided to kill + restart our processes and managed to re-established connectivity without any issues back at channel 1.

As such, we are inclined to believe that there isn’t any issues on the TREP edge server end.


We are concerned if such errors messages are due to any missing parameters within the EmaConfig.xml file perhaps?


Thank you.


Regards,

Alan

elektronrefinitiv-realtimeelektron-sdktreprrtema-apielektron-message-api
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Answer

Upvotes
Accepted
32.2k 40 11 19

Hello @AlanAng,

Looks like you are connecting to ELEKTRON via local, deployed TREP?

Elektron SDK, EMA, what version?

Running a custom EMA consumer?

I think that if the consumer was working normally prior to the disconnect, have experienced the disconnect and, once restarted, was able to reconnect, all using the same EmaConfig.xml, then EmaConfig.xml should be valid. However, please attach (ok to substitute any info with XXX) will try to verify.

Was your configuration or application modified recently?

If you are connecting via deployed TREP, managed by your organizations' market data group, perhaps it would make sense to verify with them, that there were no intermittent outages at the time of this occurrence?

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.