RTO EMA C++ consumer destructor 'Segmentation fault (core dumped)'

Considering this code snippet:
1.png

For the destructor method, it got the following 'Segmentation fault (core dumped)' error:

2.png

So the question is

1) is that allow to call the destructor (to cleanup) of the consumer and then create a new one theoretically? And why we see those error?

2) For EMA C++, is that true the handler (onRefreshMsg, onStatusMsg,...,) logic runs in a separate thread other that the 'main' thread?
3) Is there any case that EMA cannot recover the connection and quit the application (even set the attemptLimit = -1)?

4) In the case of Login Stream CLOSED due to some issue, does the application need to destroy the old consumer and create a new one, how to do that in the onStatusMsg method implementation?

Tagged:

Best Answer

  • umer.nalla
    umer.nalla LSEG
    Answer ✓

    Hi @Frederic

    As per your final question above, on a Force Logout from Dacs where the Login Stream is closed, you would need to delete the OmmConsumer and create again to initiate a new connection + login etc.


Answers