Issue with RFA loader

Hi Reuters team,
As part of Reuters connectivity I am using rfaj7.2.0.E3 api to connect to the Reuters server.
To bind to the Reuters server I am supplying the binding details in the form of the xml file which contains the server name and the port but somehow the binding is not happening and so I am not able to connect to the Reuters server.
Could you please let me know a way to debug this issue as the bank would be migrating to the new Reuters server and hence we must have the connection in place.
Thanks,
Bikash
Best Answer
-
Hello @burnwal.bikash
Can you telnet on the machine running the RFA application to the Reuters server with the sever name and the port specified in the xml file successfully?
If “Connecting To <server>...Could not open
connection to the host, on port <port>: Connect failed” is shown. The server may be down, please contact Thomson Reuters Account team. Otherwise, the
application may not be able to reach the server/port due to network/firewall problem,
please contact your Network’s admin.If you can telnet to Reuters server successfully, RFA Java trace log when the problem occurs is required for investigating the problem.
You can enable RFA Java trace log by setting ipcTraceFlags=7, mountTrace=true and logFileName to be the log file. The default path of the log file is the application run directory. For example:
<entry key="mountTrace" value="true"/>
<entry key="ipcTraceFlags" value="7"/>
<entry key="logFileName" value="rfa.log"/>0
Answers
-
Hello @burnwal.bikash
Please make sure that the server name and the port in the xml file is correct. You can confirm this info with Thomson Reuters Account team.
0 -
Hi,
I did the telnet check and I am able to connect to the server, so I am failing to understand the reason why the binding is failure.
As you have mentioned that I can enable the trace but how:
1. Do I need to create a log file under the app directory and use the details as below:
<entry key="mountTrace" value="true"/>
<entry key="ipcTraceFlags" value="7"/>
<entry key="logFileName" value="rfa.log"/>2. do we have a log file which we can use and put the above trace details to debug the issue.
Thanks,
Bikash
0 -
Hello @burnwal.bikash
You do not need to create a log file or have a log file because RFAJ will create a new log file automatically when you start running RFAJ application.
0 -
Hi,
No I was not able to review the log as I am not clear to which file I should be putting those trace details so that when I start the RFA related services I can see/monitor the details and get the information.
Can you help.
Thanks,
Bikash
0 -
Hello @burnwal.bikash
Do you mean you do not know which file you should add ipcTraceFlags=7,
mountTrace=true and logFileName to be the log file?If so, these configuration parameters should be put in the
same node that contains the server name/port where the application connects to. The node is in the xml file that the application
reads to load RFA configuration.For example: The application connects to adsserver port
14002 specified in node consConnection. Hence, the configuration parameters
should be put in consConnection node as shown below.<node name="consConnection">
<map>
<entry key="connectionType" value="RSSL"/>
<entry key="serverList" value="localhost"/>
<entry key="portNumber" value="14002"/>
<entry key="mountTrace" value="true"/>
<entry key="ipcTraceFlags" value="7"/>
<entry key="logFileName" value="rfa.log"/>
</map>
</node>If you do not know which file the application reads to load
RFA Configuration, you should contact the development team who develops this
application.0 -
Hi,
Thanks for the prompt answer. Now I know where to put those log details.
Thank you,
0 -
Hi,
Please see the attached file which I have modified to generate the log trace. After starting the services I could not see any log file being generated in the application directory or any such possible directory.
Can you advice the reason for this. Do I need to change anything for the trace file to be generated.
Thanks,
Bikashrfa-configuration.zip
0 -
Hello @burnwal.bikash
I have tested the given
configuration, the RFAJ trace log file can be generated according to the trace
log configuration in the node named “ssl” that you have added. It is possible
that the application does not read this node.Apart from “ssl” node, the
remaining sessions point to the following connection node names:- ssl_selectfeed
- rssl_selectfeed
- rssl
- ssl_test
- ssl_test2
- morningstar_ssl,
- morningstar_rssl
- ReplayConnection
Hence, I suggest you add ipcTraceFlags=7,
mountTrace=true and logFileName=rfa_<connection_node_name>.log in the all
connection nodes above. For example, in
the node named “rssl”<node name="rssl">
<map>
<entry key="connectionType" value="RSSL"></entry>
...
<entry key="ipcTraceFlags" value="7" />
<entry key="logFileName" value="rfa_rssl.log" />
<entry key="mountTrace" value="true" />
</map>
</node>This will make sure that the
RFAJ trace log file will be generated regardless the application reads which
connection node.If the log file is not still
generated after you add trace log configuration parameters to the remaining
connection nodes, it is possible that the application reads RFA configuration
from another file or another way. Hence, you should contact the development
team/support who takes care of this application to ask about where the application
reads RFA configuration and how to update the RFA configuration read by the
application.0 -
Hi,
Thanks for the details. I was able to generate the log trace but my problem still persists as I could not find much details inside it like which Reuters RFA jar is being used to connect to the Reuters server.
Thanks,
Bikash
0 -
Hello @burnwal.bikash
Could you attach RFA log trace file when the problem occurs? Then, I will be able to help you to analyze it to find out why your application cannot connect to the Reuters server.
0 -
Hello @burnwal.bikash
If the problem still occurs, please send us RFA log trace file when the problem occurs. Then, I will be able to help
you to analyze it to find out why your application cannot connect to
the Reuters server.0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 167 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 688 Datastream
- 1.4K DSS
- 624 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
- 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
- 692 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
- 105 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 10 Wealth Management Web Services
- 91 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛