RFA7.2 failed to connect RMDS in Linux 6.4
Greetings
Currently, we are migrating our RFA7.2 based program from windows to Linux, but we found connection issue as below:
Received CONNECTION_EVENT:
myNamespace::SLLConnection
{ state: DOWN, code: NONE, text: "Not connected:
com.reuters.mainloop.DispatchException: Could not determine position"}
RFA: Version = 7.2.0.L1.all, Date
= Mon May 16 15:42:38 CST 2016, Jar Path = No jar file available. Executed
using class files.
DACS: Version = 7.0.1.F4, Date = Mon May 16 15:42:48 CST 2016, Jar Path = Is
bundled into rfa.jar
Also, we've has done the following check:
1) Java in Linux is 1.6
2) RMDS is accessible from Linux
3) iptables is closed.
4) configuration has been imported via Java.util.Preferences.
Any idea what happened, or any suggestion for us to debug?
Thank you very much for any reply.
Best Answer
-
This looks like the old issue I have found in RFA application on Red Hat Linux when RFA called the java function, InetAddress.getLocalHost() but it failed and threw the error message which indicated that Java could not found IP address of the local host. The old issue was fixed by including these following lines to /etc/hosts file
127.0.0.1 localhost.localdomain localhost
<assigned_ip> < hostname>
-The <assigned_ip> is a site-local IP address e.g. 192.168.x.x. or 10.x.x.x.
-The <hostname> is what returned from hostname command.
Hope this can solve your problem.
0
Answers
-
Currently, we are migrating our RFA7.2 based program from windows to
Linux,but in development environment,everything is ok,but when I deploy
the project to the ST environment,it failed to connect RMDS,I compare
and the only difference is the /etc/hosts file,but I have no permissions
to amend the hosts file in ST,the connection issue as below:Received CONNECTION_EVENT: myNamespace::SLLConnection
{ state: DOWN, code: NONE, text: "Not connected: com.reuters.mainloop.DispatchException: Could not determine position"}Any suggestion for us to debug?
0 -
@shishuoxinyux
Based on my experience, the problem can be solved by editing /etc/hosts file according to my suggestion above. Hence, please contact the admin of ST environment for editing the /etc/hosts file.
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
- 690 Datastream
- 1.4K DSS
- 629 Eikon COM
- 5.2K Eikon Data APIs
- 11 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 255 ETA
- 559 WebSocket API
- 39 FX Venues
- 15 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 25 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 279 Open PermID
- 45 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 716 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
- 106 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 95 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛