I have a service visible in ADS monitor which initially has status UP when publisher connects to ...

...ADH but which subsequently goes down after about 3 minutes of normal activity
Hello,
I would very much appreciate your assistance with an issue that I have been trying to solve for about 5 days now. If you need additional information then please let me know.
I have recently upgraded to ADH/ADS 3.5.1 on RHEL 7.6. Previously I had been using ADH/ADS 2.6.1 on RHEL 5.11 in a configuration that operated without issue. Taking that original configuration and replacing the ADS/ADH 2.6.1 with ADH/ADS 3.5.1 has led to a new situation where the connection between the publisher and ADH (whilst remaining in a good state throughout, AFAIK) somehow causes ADS to automatically close the service after about a 3 minute period of good operation.
The provider application which connects to ADH is using RFA 7.6 from a windows 10 platform, although, this issue also arises from Providers local on the same LINUX host ( a guest operating system in a Virtual Box VM hosted on Windows 10)
I have added the log files produced by ADH and ADS and the cnf file used.
Thanks for your help,
David
Best Answer
-
Hello @iain.cadman
Does the problem occur if you switch the ADH (just ADH) back to version 2.6.1? I am asking this question because there is a lot of changes in your environment (change OS, RTDS components, etc). Are there any changes on the RFA Provider application side?
When the problem occurs, did the service between ADH and Provider is still UP?
If you can replicate the issue on demand, please enable the RFA trace file and share the file when the problem occurs
RFA Java:
You can configure the following RFA Java configurations to enable the log file
- <namespace>/Connections/<Connection Name>/ipcTraceFlags = 7
- <namespace>/ Connections/<Connection Name>/mountTrace = True
- <namespace>/ Connections/<Connection Name>/logFileName=<path to log file>
RFA C++:
- \Connections\<Connection Name>\traceMsgToFile = true
- \Connections\<Connection Name>\traceMsgDomains = "all"
- \Connections\<Connection Name>\traceMsgMaxMsgSize = 10000000
- \Connections\<Connection Name>\traceMsgMultipleFiles = true
- \Connections\<Connection Name>\traceMsgFileName = <path to log file>
0
Categories
- All Categories
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 682 Datastream
- 1.4K DSS
- 613 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 248 ETA
- 552 WebSocket API
- 37 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 626 Refinitiv Data Platform Libraries
- 5 LSEG Due Diligence
- 1 LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 191 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 83 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛