question

Upvotes
Accepted
Winfried1 Schleipen01 avatar image
3 ●1 ●1 ●1

RFA 7.7 C++ libRFA_Adapter.so contains absolute path to libTibMsg

I have changed an application that used the older 32bit RFA 6.5 C++ on RedHat Linux to use the current version 7.7. This resulted in a problem with libRFA_Adapter.so trying to open libTibMsg.so from an absolute path outside the RFA installation. The library file does not have an rpath set but it contains the full path as a string:

/opt/rfa/rfa7.7.0.L1.linux.rrg/Libs/RHEL6_32_GCC444 ] strings libRFA_Adapter.so | grep jenkins
/local/jenkins/workspace/RFACPP_762_Core/OS/RH6-32/tapi/prod/x86_Linux_6X/gnu44-o/lib/lib_so/libTibMsg.so

QUESTION:

Can I prevent the RFA_Adapter from trying to open the TibMsg library from that path by configuration or is this behaviour hard coded? In my view, the latter case would mean that Refinitiv should provide a new version without this behaviour. Would you be able to do so?


My current workaround is to create the full path and link the library from the RFA installation directory. I would very much like to avoid this in a later production installation.

Thank you very much in advance for any suggestions.

Kind regards,

Winfried Schleipen


treprfarfa-apic++32-bit
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Answer

· Write an Answer
Upvotes
Accepted
Jirapongse avatar image
83.1k ●281 ●53 ●77

@Winfried1 Schleipen01

You are correct. It could be a problem in RFA 7.7.0.L1.

I have checked RFA 7.6.2.L1 and found that libRFA_Adapter.so doesn't depend on /local/jenkins/workspace/RFACPP_762_Core/OS/RH6-32/tapi/prod/x86_Linux_6X/gnu44-o/lib/lib_so/libTibMsg.so. 

[root@localhost RHEL6_32_GCC444]# ldd libRFA_Adapter.so.7
        linux-gate.so.1 =>  (0x00824000)
        libRFA_Config.so => not found
        libRFA_Logger.so => not found
        libRFA_Common.so => not found
        libRFA_Connections.so => not found
        libRFA_Connections_MD.so => not found
        libTibMsg.so => ./libTibMsg.so (0x0072b000)
        libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00893000)
        libm.so.6 => /lib/libm.so.6 (0x0046d000)
        libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00386000)
        libc.so.6 => /lib/libc.so.6 (0x00110000)
        /lib/ld-linux.so.2 (0x009b6000)

While libRFA_Adapter.so in RFA 7.7.0.L1 depends on /local/jenkins/workspace/RFACPP_762_Core/OS/RH6-32/tapi/prod/x86_Linux_6X/gnu44-o/lib/lib_so/libTibMsg.so. 

[root@localhost RHEL6_32_GCC444]# ldd libRFA_Adapter.so.7
        linux-gate.so.1 =>  (0x00a55000)
        libRFA_Config.so => ./libRFA_Config.so (0x00110000)
        libRFA_Logger.so => ./libRFA_Logger.so (0x00f4d000)
        libRFA_Common.so => ./libRFA_Common.so (0x0015d000)
        libRFA_Connections.so => ./libRFA_Connections.so (0x0052f000)
        libRFA_Connections_MD.so => ./libRFA_Connections_MD.so (0x003a1000)
        libTibMsg.so => ./libTibMsg.so (0x00590000)
        /local/jenkins/workspace/RFACPP_762_Core/OS/RH6-32/tapi/prod/x86_Linux_6X/gnu44-o/lib/lib_so/libTibMsg.so => not found
        libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00721000)
        libm.so.6 => /lib/libm.so.6 (0x00aea000)
        libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x001b2000)
        libc.so.6 => /lib/libc.so.6 (0x001d0000)
        librt.so.1 => /lib/librt.so.1 (0x00360000)
        /lib/ld-linux.so.2 (0x009b6000)
        libpthread.so.0 => /lib/libpthread.so.0 (0x00369000)

Please submit this case to the RDC support team via Contact Premium Support to verify and fix this issue.


1620188014203.png (97.6 KiB)
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Winfried1 Schleipen01 avatar image Winfried1 Schleipen01

Hello, thanks for confirming my findings. I hope that the RDC support team will be able to solve the issue. Until then, my request is unfortunately not solved. But your response was nonetheless helpful for me.

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.