F9: Server has gone down. Will recall when a server becomes available
We have are getting data from IDN_SELECTFEED and we have created a conflation service based from IDN_SELECTFEED called IDN_X and we have 4 ROUTES to retrieve data from IDN_SELECTFEED
When RTO Route is disconnected IDN_SELECTFEED is able to seamlessly get data from other RTO Routes. However, for IDN_X it will occur: F9: Server has gone down. Will recall when a server becomes available
How can we resolve this IDN_X issue?
Best Answer
-
Hello @weishengtay
Thank you for the confirmation. The F9 message indicates that something went wrong on the ADS (possibly the feed one) side when it encounters the route disconnected.
Did you check the IDN_X service status in the adsmon tool whether it is UP or DOWN?
I strongly suggest you contact the ADS support team to verify the issue on the ADS side.
0
Answers
-
Hello @weishengtay
Could you please explain more about your connection and the product that encounters the issue?
I am assuming that you are using the deployed ADS with the service name IDN_SELECTFEED which source data from RTO like the following diagram:
- Service IDN_SELECTFEED: Consumer API (RFA or RTSDK) --> ADS --> RTO
- Service IDN_X: Conflate from above service
When one RTO Route gone down, the IDN_X service got "F9: Server has gone down. Will recall when a server becomes available" message and never back to UP again, am I correct?
Please be informed that the "F9: Service has gone down. Will recall when service becomes available." message is generated from the ADH server. According to the ADH document, the message appears if a service goes gone down, the ADH logs this status text, and any ADS in Broker mode sends this status text.
On the API part, if an application receives this status with DataState = Suspect; StreamState = Open state, the Real-Time APIs (RFA and RTSDK) automatically recovers the item subscription for an application. An application does not need to re-subscribe item manually. However, if the service does not recover (back to UP), I strongly suggest you contact the ADS support team to verify the issue on the server side.
You can contact the ADS support team via https://myaccount.lseg.com/en/helpandsupport website.
I hope this information helps.
0 -
Hello @wasin.w,
Your understanding is right, however we are using ADS pop configuration
- Service IDN_SELECTFEED: Consumer API (RFA or RTSDK) --> -> ADS (hub) -> ADS (feed) --> RTO / EDGE
- Service IDN_X: Conflate from above service
At the ADS Feed layer, we have 4 IDN_SELECTFEED routes and at the ADS Hub layer, we have IDN_SELECTFEED as well as IDN_X conflate from IDN_SELECTFEED.
The current scenario is that at the Hub layer:
1. Both Consumer API side and ADS Hub (testclient demo tools with -X) - if service is IDN_SELECTFEED, it will seamlessly retrieve data from the other IDN_SELECTFEED routes
2. However, when the service is switched from IDN_SELECTFEED to IDN_X, the error: F9: Service has gone down. Will recall when service becomes available. persist and does not retrieve data from other routes
0 -
We have verified the IDN_X service status in adsmon is still showing state "Up".
In addition, we have tested in our dev environment, the error still persist. We simulate the behaviour and discovered that it took about 1 min to recover the service when the affected RTO is back to "Active" . It did not take data from the other IDN_SELECTFEED
0
Categories
- All Categories
- 6 AHS
- 37 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
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛