Segmentation fault when recv exit signal when using warm standby feature

I have uploaded my warm-standby emaconfig.xml file. It appears that the configuration item <EnableSessionManagement value="1"/> significantly affects the app's behavior.

Is the WSB feature mandatory for using <ChannelType value="ChannelType::RSSL_ENCRYPTED"/> and <EnableSessionManagement value="1"/>?

emaconfig.txt

I extracted the items above by referring to the 470 tutorial. When I don’t use the WSB feature, no segmentation fault is triggered—this is based on the 113 tutorial.

My app's simplified entrance code show below. Could you please point out my problems?

ps:

I find that SIGINT is used by EMA framework itself, so I use SIGTERM for elegant exit for my own app.

app.txt

Find more posts tagged with

c++

ema-api

#technology

Accepted answers

All comments

Jirapongse

@liukehan

Thank you for reaching out to us.

No, the WSB feature is not mandatory for using <ChannelType value="ChannelType::RSSL_ENCRYPTED"/> and <EnableSessionManagement value="1"/>.

The WSB is an additional feature to make the application more resilience. Please refer to this Introduction to Refinitiv Real-Time SDK Warm Standby Feature article.

I tested the Cons113 with the WSB configurations and it can run properly.

EmaConfig.xml.txt

To investigate this issue, you may use the latest version of RTSDK C/C++ (RTSDK C/CPP 2.3.2.L1 aka EMA/ETA 3.9.2.L1 aka 3.9.2.0).

You can download it from the LSEG Developer Community Website

liukehan

Thanks for your kind help.

Quesion 1:

I have read this Introduction to Refinitiv Real-Time SDK Warm Standby Feature article. According to 《LSEG DOMAIN MODEL USAGE GUIDE》4.6.1 section, The Directory request is sent after the Login is successful. Response message for this directory request are not forwarded to the consumer application. If the consumer wants source directory information, it is required to make its own request for the Directory.

"In the article, regarding service-based warm standby, will the status messages indicating 'service down' and 'warm standby up' be forwarded to the consumer application?" ( The 9th and 12th step)

Quesion 2:

"Per section 3.4.5 of the LSEG DOMAIN MODEL USAGE GUIDE, when SINGLEOPEN = 1 and ALLOWSUSPECTDATA = 1, does the explanation of stream state and data state features in section 3.4.5 apply only to the login stream, or does it extend to all streams (including market data streams, dictionary streams, directory streams, and login streams)?" This means I only need to handle the dataState, as the streamState will always remain OPEN.

Quesion 3:

A pre-sales technical engineer from Reuters once communicated with me that the segmentation fault when recuv exit signal when using warm standby feature issue was caused by me configuring two <Channel> with <EnableSessionManagement value="1"/> simultaneously, resulting in multiple releases within the EMA framework. Suggest that I remove the <EnableSessionManagement value="1"/> of the standby channel. And it really solve the segmentation fault. What do you think. Here is a screenshot of the results of my addressSantinizer.

AddressSantinizer.txt

EXPLORE OUR SITES