The system error 10054 from Win32 is:

WSAECONNRESET (10054) Connection reset by peer. A existing connection was forcibly closed by the remote host.

Thus the provider you are connecting to is forcibly closing your connection. For the reason you must peruse the provider logs, if an ADS you may need help from your administrator possibly requiring elevated log levels.

Typical cause in production is a slow consumer, i.e. you are not processing incoming updates fast enough causing a back log in the ADS. One resolution for this is for the administrator to enable just-in-time-conflation which will conflate updates that are waiting delivery.

Typical cause in development is that you are not following the RDM protocol correctly and the provider has not understood what you have sent it and thus drops the connection to reset the state.

How many threads are calling

void onUpdateMsg( constthomsonreuters::ema::access::UpdateMsg&, constthomsonreuters::ema::access::OmmConsumerEvent& );

in the configure, do I have a way to increase the number of thread calling the

onUpdateMsg(call back) func? thanks.

@James.Shen

In EMA, there are two operation modes:

• OmmConsumerConfig::ApiDispatchEnum: In this mode, EMA will create a second, internal thread to dispatch received messages to the callbacks

• OmmConsumerConfig::UserDispatch: In this mode, the application is responsible for calling the Ommconsumer::dispatch() method to dispatch all received to the callbacks. However, calling Ommconsumer::dispatch() from multiple threads is not recommended because it can introduce ordering issues associated with information received, which may or may not impact ordering of related messages.

In conclusion, for one OmmConsumer, it should have only one thread that dispatches received messages to the callbacks.

To use multiple dispatch threads, you can create multiple instances of OmmConsumer. For more information, please refer to 410__MarketPrice__HorizontalScaling example in EMA package