Getting StatusText":"Service route SERVICE is no longer available."
we are using RFA Java Edition 8.1.0.L1.all.rrg to connect to an ADS
One of the services the ADS went down briefly, and we noticed below in "update" messages for a subscription to a different service
24-02-21 12:38:34,403 [MainThread] ERROR in {Process name}. Dequeued update: {"BID":153.9,"ASK":155.35,"BIDSIZE":51.0,"ASKSIZE":51.0,"QUOTIM":"2024-02-21 12:38:29.000-0500","QUOTIM_MS":63509000,"PRC_QL_CD":"AUT","MessageType":"UPDATE","Service":"SERVICE_1","Item":"RIC1","StreamState":"CLOSED_RECOVER","DataState":"SUSPECT","StatusCode":"NO_RESOURCES","StatusText":"Service route SERVICE_2 is no longer available.","SeqNum":464,"PassThru":{}}
Is this normal? does ADS keep sending this statusText until the down service comes back?
Best Answer
-
Thank you for reaching out to us.
The update response should not contain the status informaion (StreamState, DataState, StatusCode, and StatusText). Typically, the status information is available in the refresh and status responses.
How did you get the status information from the update response?
The streamState is CLOSED_RECOVER which indicates that the stream for this item is closed. The item may be available later and the application can attempt to re-open this item on another stream. This means that the application needs to re-subcribe to this item to get data and RFA will not recover this item.
Actually, this is not normal. When the service is down, the streamState should be still opened and the dataState will be suspect.
"StreamState":"CLOSED_RECOVER","DataState":"SUSPECT","StatusCode":"NO_RESOURCES","StatusText":"Service route SERVICE_2 is no longer available.",
However, it may relate to many factors, such as ADH/ADS configurations and RFA Java configurations.
As far as I now, the API will send this status information to all subscribed streams but the API will not recover those streams because the streamState is CLOSED_RECOVER.
Please share the RFA Java configurations so we can verify the configurations.
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 中文论坛