Getting out of buffer exception due to slow consumer (EMA C++ OMM API)

kwunyu.wu

I'm building a interactive provider (EMA C++ OMM API) for streaming the market data to different downstream applications, which are Refinitiv Consumer, through TCP socket.

I'm testing the scenario that how my provider behaves when I have very slow consumer connect to it.

I found that the provider will throw an out of buffer exception when I submit the updateMsg.

I'm wondering if there are configurations or control throw that can allow the provider to detect and drop the slow consumer connection such that to avoid the out of buffer exception.

The following is the error message I found in the core dump:

"Internal error: rsslReactorSubmitMsg() failed in OmmIProviderImpl::submit( const UpdateMsg& ).
Error: 1009 ipcDataBuffer() failed, out of output buffers. The output buffer may need to be flushed.

Jirapongse

@kwunyu.wu

Thanks for reaching out to us.

The provider applications are unable to detect that the connected consumer applications are slow consumers because the provider applications don't know how fast the consumer applications process the data. Moreover, typically, the consumer applications themselves don't know that they are slow consumers until the connections have been disconnected.

The application submits data to the API's buffers then the API frees the buffers by flushing data to the network. The out-of-buffer exception indicates that the API was unable to flush data to the network. The cause of the exception could be a network issue or a slow consumer.

I don't think that the EMA API has configurations or other methods to detect slow consumers. RTDS (ADS) also uses the buffer overflow condition to cut channels.

I hope that this information is of help.