Encounter Text Message Encoding Failure on client side

We have tried to deploy the EMA C++ Provider/Consumer on some RHEL 8.7 servers, with EMA version 3.6.5, and we got the following error on client side:

loggerMsg
    TimeStamp: 20:04:36.916
    ClientName: ChannelCallbackClient
    Severity: Success
    Text:    Received ChannelUp event on channel Channel_1
        Instance Name Consumer_1_1
        Connected component version: eta3.6.5.L1.rrg|ema3.6.5.L1.linux 64-bit Static(Optimized)
loggerMsgEnd

loggerMsg
    TimeStamp: 20:04:36.916
    ClientName: ChannelCallbackClient
    Severity: Warning
    Text:    Received ChannelDownReconnecting event on channel Channel_1
        Instance Name Consumer_1_1
        RsslReactor 0x0x251a740
        RsslChannel 0x0x251a740
        Error Id -29
        Internal sysError 0
        Error Location /local/jenkins/workspace/ESDKCore_RCDEV/OS/OL7-64/rcdev/source/rtsdk/Cpp-C/Eta/Impl/Reactor/Watchlist/rsslWatchlistImpl.c:4863
        Error Text Message encoding failure -- -29.
loggerMsgEnd

We have enabled the XML debug log on the EmaConfig file on the provider side, and it only shows the "closed channel".

We have done some investigations and we found that not all RHEL 8.7 server has the issues. During the investigation, we are using the same binaries/config/dictionary/enumDef, so the behavior is exposed to be consistent but it is not. Some servers are working properly and some of them are not.

Did anyone encounter this issue before?

Find more posts tagged with

c++

ema-api

interactive-provider

redhat-enterprise-linux

#technology

Accepted answers

Jirapongse

@kwunyu.wu

Thanks for reaching out to us.

First of all, you may need to upgrade the application to use the latest version of RTSDK. The latest version is RTSDK C/CPP 2.1.1.L1 aka EMA/ETA 3.7.1.L1. You can download it from the Refinitiv Developer Portal or Software Downloads. The API is in the MDS - API product family

If the problem still happens with the latest version of the API. You may need to contact the API support team to investigate this issue.

According to the error code (-29), it is RSSL_RET_INVALID_DATA which indicates that invalid data was provided to the invoked function. You may need to verify how the application creates request messages.

All comments

Jirapongse

@kwunyu.wu

Thanks for reaching out to us.

If the problem still happens with the latest version of the API. You may need to contact the API support team to investigate this issue.

kwunyu.wu

Thank you for your suggestions.

Let us try to upgrade the SDK and test it again. We will get back to you later.

For the request messages creation logic, I think it should be correct as it does work in some servers for the same binaries of the application.

EXPLORE OUR SITES