RFA Login Slow

Hello
Wrote a simple java application which connects to Reuters RMDS Instance. I ran the same process from windows and unix instance. The windows instance is much faster compare to Unix. Simple steps like acquiring session and getting a response back for login request takes more time in unix compared to windows. We are taking abt order of few sec in windows as opposed to mins(2-3 mins) in Unix. Are we supposed to use diff rfa jar file when runnning from different operating systems. We are using rfa 8.0.0 jar file for our purposes
Best Answer
-
Hello Lars/Wasin
Thanks for the reply.Managed to resolve it on my side.The problem was due to Java preference package. The unix user profile running the process was mounted on a n/w which was in different region. I reconfigured -Djava.util.prefs.systemRoot and Userroot to a local directory to make it work.
0
Answers
-
Hello @prakash.chellappa
- Could you please enable the RFA trace file, replicate the problem and give us both trace files from Windows and Unix?
- Do both Windows and Unix connects to the same TREP instance?
- What is the Unix/Linux OS that you are using?
- Could you please also test with RFA Java 8.1.0 which is the latest version of RFA Java?
You can enable the RFA trace file via the following RFA Java configurations
<namespace>/Connections/<Connection Name>/ipcTraceFlags = 7
<namespace>/ Connections/<Connection Name>/mountTrace = True
<namespace>/ Connections/<Connection Name>/logFileName=<path to log file>0 -
Very unlikely to be related to RFA or TREP.
Guess: Most likely it is the name resolution on Unix box which is taken the time. It may be configured differently than on your Windows box.
Action: For each of the entries in your 'serverList' config test how long time your Unix box takes to resolve them. Tool nslookup is your friend.
Also the network routes to whatever is in your 'serverList' may be different between your Windows box vs your Unix box. Tool traceroute/tracert.exe is your friend.0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 687 Datastream
- 1.4K DSS
- 622 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
- 255 ETA
- 557 WebSocket API
- 38 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
- 276 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
- 680 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- 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
- 27 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 91 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛