New posts are disabled while we improve the user experience.
You can browse the site, or for urgent issues, raise a query at MyAccount.
1
●0 ●0 ●1
RFA Internal failure / Pls see details
hi - please help identify this issue : This is the error we got trying to connect to ads to our internal trep host We like to understand what these RFA error mean? Can you please let us know? [2020-09-08 12:51:23] RFA Internal failure [2020-09-08 12:51:23] [2020-09-08 12:51:23] Application: RFA [2020-09-08 12:51:23] Process Id: 0x6F57 [2020-09-08 12:51:23] [2020-09-08 12:51:23] File: Session_OMM/Impl/OMMSrcDirectoryMsgHandler.cpp [2020-09-08 12:51:23] Line: 2892 [2020-09-08 12:51:23] [2020-09-08 12:51:23] Problem: [2020-09-08 12:51:23] RFA_VERIFY( (!((rsslEncodeElementListElementInit(&eIter, &element, 0)) < 0 )) ) failed [2020-09-09 07:13:30] RFA Internal failure [2020-09-09 07:13:30] [2020-09-09 07:13:30] Application: RFA [2020-09-09 07:13:30] Process Id: 0x7F8 [2020-09-09 07:13:30] [2020-09-09 07:13:30] File: Session_OMM/Impl/OMMSrcDirectoryMsgHandler.cpp [2020-09-09 07:13:30] Line: 2892 [2020-09-09 07:13:30] [2020-09-09 07:13:30] Problem: [2020-09-09 07:13:30] RFA_VERIFY( (!((rsslEncodeElementListElementInit(&eIter, &element, 0)) < 0 )) ) failed ====================== This is what we got from the lib files: VERSION 6.3.1 RELEASE (Internal Node: rfaut6.3.1.F4)
libRFA_Common.so version.c VERSION 6.3.1 RELEASE (Internal Node: rfaut6.3.1.F4) @(#)version.c Reuters Foundation API (RFA) 6.3.1 RELEASE
libRFA_Config.so version.c VERSION 6.3.1 RELEASE (Internal Node: rfaut6.3.1.F4) @(#)version.c Reuters Foundation API (RFA) 6.3.1 RELEASE
25.4k
●90 ●13 ●26
Unfortunately, RFA v6.3 has not been supported for several years now (it is around 10-11 yrs old).
Currently, the oldest supported version is v7.6.x
Based on the information in your post, the issue appears to be related to the decoding of the Service (source) directory message from the ADS.
I am guessing that this only started happening recently? If so, can you confirm with your Market data team:
- Was the ADS upgraded recently?
- Were any new services (sources) added to the ADS recently?
In the past, I have seen this when the number of services on the ADS exceeded the limit of the older version of the RFA API. I also saw this a few years ago where the RFA application was using two OMMConsumer instances and they were sharing a connection - but this was observed in an older RFA 7.x release).
If one of the above changes was made to your ADS, you could ask your MDS team if they can allow you to connect to an older version of ADS or one with fewer services available - for the short term. This could offer you some breathing space to upgrade to a new version of RFA e.g. v7.6 or ideally v8.x
1
●0 ●0 ●1
Hi
Sorry for late reply and thanks for your input.
How many sources can be added to ads before the applications fails?
We have a lot of sources on the ADS.
Initially the application connects to the ads but i drops.
Thanks I look forward to hear from you
25.4k
●90 ●13 ●26
Did you confirm with your Market Data team if they recently added new sources as per my earlier post? Please confirm this before we explore this as the reason for your application failure.
If you have confirmed that sources were recently added, then I will need to do some digging to confirm what the limit was - is quite an old issue which was fixed several years. However, my suspicion is that the number was something like 64 or 128?
I will try and confirm the number and get back.
However, you really should be upgrading to a newer version of RFA - as mentioned v6.3 has not been supported for several years now.
