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
Best Answer
-
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?
0
Categories
- All Categories
- 6 AHS
- 39 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 60 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛