RFA 7.8 SSLED message tracing (32 bit)

Options
Winfried1 Schleipen01
Winfried1 Schleipen01 Newcomer
in RFA

Hello,

we have an application subscribing price data via an old RFA SSLED connection to a TREP server using RFA V7.8 in 32 bit.
We have a requirement to setup message file tracing for performance measurement from the server operator.
I have tried several approaches suggested (one from this forum for verbose logging in SSLED) but nothing works as I would expect. When I add an sslapi.cnf file with


*messageTracingFlags: SSL_TRACE_IN SSL_TRACE_DATA
*messageTracing:20000000
*functionLogging:20000000
*eventLogging:20000000

I get a message trace, but on the terminal, not into a file.

QUESTION: What configuration changes do I have to make to get the trace into a file. Terminal logging is no option as we need to trace in the production environment.


Thank you very much in advance for any helpful suggestions.

Tagged:

Answers

  • Gurpreet
    Gurpreet admin

    Hello @Winfried1 Schleipen01,

    RFA is a legacy API and the SSL protocol is the End of Life as per this product change notification. I would recommend that you look into migrating the app to a recent, supported SDK like RealtimeSDK for Java or C++. These SDKs are easier to program, compared with RFA, and your SSL based application will stop working, once the infrastructure is upgraded.

    For your question, I didn't think that sslapi.cnf was applicable to RFA SDK. RFA has its own logger entries in the RFA configuration, under the section App Logger - which specify the filename, size etc. Please check the RFA Config Guide which is bundled with your RFA SDK package.

    See this question for a basic usage of the App logger entries.

  • Winfried1 Schleipen01
    Winfried1 Schleipen01 Newcomer
    https://community.developers.refinitiv.com/discussion/comment/122862#Comment_122862
    Hello Gurpreet,

    thanks for your response. I am aware that the RFA is legacy. Sometimes circumstances prevent you from changing to a newer proctol. So that will not change for the moment.
    M observations are from our live systems, I have tried to follow the RFA documentation first. The RFA Logging is documented for RSSL connections but we have to use SSLED, for which message tracing is apparently not controlled from the RFA configuration.
    I have found another post in this forum (Verbose Logging SSLED) which detailed the switch on of tracing in SSLED and tried that. Also some settings suggested by the operators of the TREP server we connect to. To no avail, all tracing is done on the terminal, which is not what we need here.

    So I am looking for information on how to direct the message tracing, which is definitely switched on using the sslapi.cnf file, to a file instead of to the console. I have tried every configuration parameter I could find, nothing worked ...
  • Winfried1 Schleipen01
    Winfried1 Schleipen01 Newcomer

    Hello,

    I have found the cause of the tracing to the terminal. My application has no write permissions on its current working directory. I setup a test environment where it had those permissions and then it created an IPCTRACE{PID} file. It moves the file to IPCTRACE{PID}.old when 2MB size are reached.
    Now I still would like to control where the file is written so I can use a directory with the correct permissions.

  • Gurpreet
    Gurpreet admin

    Hello @Winfried1 Schleipen01,

    It doesn't look like the output directory of the file can be configured. Here is what I found in an old SFC guide:


    1731074922929.png

  • Winfried1 Schleipen01
    Winfried1 Schleipen01 Newcomer
    https://community.developers.refinitiv.com/discussion/comment/122887#Comment_122887
    Hello Gurpreet,

    thank you very much for digging this old doc out. Will have to live with that for the moment. I really hope that we will migrate to something more modern in near time ...

    Best regards,

    Winfried

Categories