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
