RFA Login Slow

prakash.chellappa
prakash.chellappa Explorer
in RFA

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

Tagged:

Best Answer

  • prakash.chellappa
    prakash.chellappa Explorer
    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.

Answers

  • wasin.w
    wasin.w admin

    Hello @prakash.chellappa

    1. Could you please enable the RFA trace file, replicate the problem and give us both trace files from Windows and Unix?
    2. Do both Windows and Unix connects to the same TREP instance?
    3. What is the Unix/Linux OS that you are using?
    4. 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>
  • Lars-at-Addicticks
    Lars-at-Addicticks Expert

    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.

Categories