An established connection was aborted by the software in your host machine

Question

question

blam

3 ●0 ●0 ●1

An established connection was aborted by the software in your host machine

hi,

We found following errors in the log. An established connection was aborted by the software in your host machine. Does that really mean the connection was terminated by host host machine?

Also, it took six seconds to recover. is there any chance we could make it shorter by config?

Many thanks,

Brian

2019-06-03 09:57:31.876 [pool-7-thread-1] WARN com.thomsonreuters.ema.access.OmmConsumerImpl - loggerMsg ClientName: ChannelCallbackClient Severity: Warning Text: Received ChannelDownReconnecting event on channel Channel_1 RsslReactor @439cd2fe RsslChannel @9b6c59b Error Id 0 Internal sysError 0 Error Location null Error text An established connection was aborted by the software in your host machine loggerMsgEnd 2019-06-03 09:57:31.876 [pool-15-thread-1] WARN com.thomsonreuters.ema.access.OmmConsumerImpl - loggerMsg ClientName: ChannelCallbackClient Severity: Warning Text: Received ChannelDownReconnecting event on channel Channel_1 RsslReactor @7fe7b7b3 RsslChannel @2aecad76 Error Id 0 Internal sysError 0 Error Location null Error text An established connection was aborted by the software in your host machine loggerMsgEnd 2019-06-03 09:57:31.876 [pool-9-thread-1] WARN com.thomsonreuters.ema.access.OmmConsumerImpl - loggerMsg ClientName: ChannelCallbackClient Severity: Warning Text: Received ChannelDownReconnecting event on channel Channel_2 RsslReactor @ef4dab4 RsslChannel @2ef09c37 Error Id 0 Internal sysError 0 Error Location null Error text An established connection was aborted by the software in your host machine loggerMsgEnd 2019-06-03 09:57:31.876 [pool-5-thread-1] WARN com.thomsonreuters.ema.access.OmmConsumerImpl - loggerMsg ClientName: ChannelCallbackClient Severity: Warning Text: Received ChannelDownReconnecting event on channel Channel_1 RsslReactor @7ed98cbb RsslChannel @42ff7057 Error Id 0 Internal sysError 0 Error Location null Error text An established connection was aborted by the software in your host machine loggerMsgEnd 2019-06-03 09:57:31.876 [pool-3-thread-1] WARN com.thomsonreuters.ema.access.OmmConsumerImpl - loggerMsg ClientName: ChannelCallbackClient Severity: Warning Text: Received ChannelDownReconnecting event on channel Channel_1 RsslReactor @621ea382 RsslChannel @6e852eb8 Error Id 0 Internal sysError 0 Error Location null Error text An established connection was aborted by the software in your host machine loggerMsgEnd 2019-06-03 09:57:31.876 [pool-17-thread-1] WARN com.thomsonreuters.ema.access.OmmConsumerImpl - loggerMsg ClientName: ChannelCallbackClient Severity: Warning Text: Received ChannelDownReconnecting event on channel Channel_1 RsslReactor @242b4783 RsslChannel @7e5e81c9 Error Id 0 Internal sysError 0 Error Location null Error text An established connection was aborted by the software in your host machine loggerMsgEnd 2019-06-03 09:57:31.882 [pool-11-thread-1] WARN com.thomsonreuters.ema.access.OmmConsumerImpl - loggerMsg ClientName: ChannelCallbackClient Severity: Warning Text: Received ChannelDownReconnecting event on channel Channel_1 RsslReactor @38e8c89b RsslChannel @33251a Error Id 0 Internal sysError 0 Error Location null Error text An established connection was aborted by the software in your host machine loggerMsgEnd 2019-06-03 09:57:31.876 [pool-13-thread-1] WARN com.thomsonreuters.ema.access.OmmConsumerImpl - loggerMsg ClientName: ChannelCallbackClient Severity: Warning Text: Received ChannelDownReconnecting event on channel Channel_2 RsslReactor @148797b2 RsslChannel @34ce4e0f Error Id 0 Internal sysError 0 Error Location null Error text An established connection was aborted by the software in your host machine loggerMsgEnd 2019-06-03 09:57:33.415 [pool-3-thread-1] WARN com.thomsonreuters.ema.access.OmmConsumerImpl - loggerMsg ClientName: LoginCallbackClient Severity: Warning Text: RDMLogin stream state was changed to suspect with status message username <not set> usernameType <not set> State: Open/Suspect/None - text: "" loggerMsgEnd 2019-06-03 09:57:33.415 [pool-11-thread-1] WARN com.thomsonreuters.ema.access.OmmConsumerImpl - loggerMsg ClientName: LoginCallbackClient Severity: Warning Text: RDMLogin stream state was changed to suspect with status message username <not set> usernameType <not set> State: Open/Suspect/None - text: "" loggerMsgEnd 2019-06-03 09:57:33.415 [pool-9-thread-1] WARN com.thomsonreuters.ema.access.OmmConsumerImpl - loggerMsg ClientName: LoginCallbackClient Severity: Warning Text: RDMLogin stream state was changed to suspect with status message username <not set> usernameType <not set> State: Open/Suspect/None - text: "" loggerMsgEnd 2019-06-03 09:57:33.415 [pool-15-thread-1] WARN com.thomsonreuters.ema.access.OmmConsumerImpl - loggerMsg ClientName: LoginCallbackClient Severity: Warning Text: RDMLogin stream state was changed to suspect with status message username <not set> usernameType <not set> State: Open/Suspect/None - text: "" loggerMsgEnd 2019-06-03 09:57:33.415 [pool-5-thread-1] WARN com.thomsonreuters.ema.access.OmmConsumerImpl - loggerMsg ClientName: LoginCallbackClient Severity: Warning Text: RDMLogin stream state was changed to suspect with status message username <not set> usernameType <not set> State: Open/Suspect/None - text: "" loggerMsgEnd 2019-06-03 09:57:33.415 [pool-13-thread-1] WARN com.thomsonreuters.ema.access.OmmConsumerImpl - loggerMsg ClientName: LoginCallbackClient Severity: Warning Text: RDMLogin stream state was changed to suspect with status message username <not set> usernameType <not set> State: Open/Suspect/None - text: "" loggerMsgEnd 2019-06-03 09:57:33.415 [pool-7-thread-1] WARN com.thomsonreuters.ema.access.OmmConsumerImpl - loggerMsg ClientName: LoginCallbackClient Severity: Warning Text: RDMLogin stream state was changed to suspect with status message username <not set> usernameType <not set> State: Open/Suspect/None - text: "" loggerMsgEnd 2019-06-03 09:57:33.415 [pool-17-thread-1] WARN com.thomsonreuters.ema.access.OmmConsumerImpl - loggerMsg ClientName: LoginCallbackClient Severity: Warning Text: RDMLogin stream state was changed to suspect with status message username <not set> usernameType <not set> State: Open/Suspect/None - text: "" loggerMsgEnd 2019-06-03 10:16:12.377 [pool-17-thread-1] WARN com.thomsonreuters.ema.access.OmmConsumerImpl - loggerMsg ClientName: ChannelCallbackClient Severity: Warning Text: Received ChannelDownReconnecting event on channel Channel_2 RsslReactor @242b4783 RsslChannel @7e5e81c9 Error Id 0 Internal sysError 0 Error Location null Error text An established connection was aborted by the software in your host machine loggerMsgEnd 2019-06-03 10:16:12.378 [pool-7-thread-1] WARN com.thomsonreuters.ema.access.OmmConsumerImpl - loggerMsg ClientName: ChannelCallbackClient Severity: Warning Text: Received ChannelDownReconnecting event on channel Channel_2 RsslReactor @439cd2fe RsslChannel @9b6c59b Error Id 0 Internal sysError 0 Error Location null Error text An established connection was aborted by the software in your host machine loggerMsgEnd 2019-06-03 10:16:12.377 [pool-11-thread-1] WARN com.thomsonreuters.ema.access.OmmConsumerImpl - loggerMsg ClientName: ChannelCallbackClient Severity: Warning Text: Received ChannelDownReconnecting event on channel Channel_2 RsslReactor @38e8c89b RsslChannel @33251a Error Id 0 Internal sysError 0 Error Location null Error text An established connection was aborted by the software in your host machine loggerMsgEnd 2019-06-03 10:16:12.377 [pool-9-thread-1] WARN com.thomsonreuters.ema.access.OmmConsumerImpl - loggerMsg ClientName: ChannelCallbackClient Severity: Warning Text: Received ChannelDownReconnecting event on channel Channel_1 RsslReactor @ef4dab4 RsslChannel @2ef09c37 Error Id 0 Internal sysError 0 Error Location null Error text An established connection was aborted by the software in your host machine loggerMsgEnd 2019-06-03 10:16:12.378 [pool-15-thread-1] WARN com.thomsonreuters.ema.access.OmmConsumerImpl - loggerMsg ClientName: ChannelCallbackClient Severity: Warning Text: Received ChannelDownReconnecting event on channel Channel_2 RsslReactor @7fe7b7b3 RsslChannel @2aecad76 Error Id 0 Internal sysError 0 Error Location null Error text An established connection was aborted by the software in your host machine loggerMsgEnd 2019-06-03 10:16:12.377 [pool-3-thread-1] WARN com.thomsonreuters.ema.access.OmmConsumerImpl - loggerMsg ClientName: ChannelCallbackClient Severity: Warning Text: Received ChannelDownReconnecting event on channel Channel_2 RsslReactor @621ea382 RsslChannel @6e852eb8 Error Id 0 Internal sysError 0 Error Location null Error text An established connection was aborted by the software in your host machine loggerMsgEnd 2019-06-03 10:16:12.377 [pool-13-thread-1] WARN com.thomsonreuters.ema.access.OmmConsumerImpl - loggerMsg ClientName: ChannelCallbackClient Severity: Warning Text: Received ChannelDownReconnecting event on channel Channel_1 RsslReactor @148797b2 RsslChannel @34ce4e0f Error Id 0 Internal sysError 0 Error Location null Error text An established connection was aborted by the software in your host machine loggerMsgEnd 2019-06-03 10:16:12.469 [pool-5-thread-1] WARN com.thomsonreuters.ema.access.OmmConsumerImpl - loggerMsg ClientName: ChannelCallbackClient Severity: Warning Text: Received ChannelDownReconnecting event on channel Channel_2 RsslReactor @7ed98cbb RsslChannel @42ff7057 Error Id 0 Internal sysError 0 Error Location null Error text An established connection was aborted by the software in your host machine loggerMsgEnd 2019-06-03 10:16:12.479 [pool-5-thread-1] WARN com.thomsonreuters.ema.access.OmmConsumerImpl - loggerMsg ClientName: LoginCallbackClient Severity: Warning Text: RDMLogin stream state was changed to suspect with status message username <not set> usernameType <not set> State: Open/Suspect/None - text: "" loggerMsgEnd 2019-06-03 10:16:12.479 [pool-7-thread-1] WARN com.thomsonreuters.ema.access.OmmConsumerImpl - loggerMsg ClientName: LoginCallbackClient Severity: Warning Text: RDMLogin stream state was changed to suspect with status message username <not set> usernameType <not set> State: Open/Suspect/None - text: "" loggerMsgEnd 2019-06-03 10:16:12.479 [pool-13-thread-1] WARN com.thomsonreuters.ema.access.OmmConsumerImpl - loggerMsg ClientName: LoginCallbackClient Severity: Warning Text: RDMLogin stream state was changed to suspect with status message username <not set> usernameType <not set> State: Open/Suspect/None - text: "" loggerMsgEnd 2019-06-03 10:16:12.479 [pool-3-thread-1] WARN com.thomsonreuters.ema.access.OmmConsumerImpl - loggerMsg ClientName: LoginCallbackClient Severity: Warning Text: RDMLogin stream state was changed to suspect with status message username <not set> usernameType <not set> State: Open/Suspect/None - text: "" loggerMsgEnd 2019-06-03 10:16:12.479 [pool-17-thread-1] WARN com.thomsonreuters.ema.access.OmmConsumerImpl - loggerMsg ClientName: LoginCallbackClient Severity: Warning Text: RDMLogin stream state was changed to suspect with status message username <not set> usernameType <not set> State: Open/Suspect/None - text: "" loggerMsgEnd 2019-06-03 10:16:12.479 [pool-11-thread-1] WARN com.thomsonreuters.ema.access.OmmConsumerImpl - loggerMsg ClientName: LoginCallbackClient Severity: Warning Text: RDMLogin stream state was changed to suspect with status message username <not set> usernameType <not set> State: Open/Suspect/None - text: "" loggerMsgEnd 2019-06-03 10:16:12.479 [pool-9-thread-1] WARN com.thomsonreuters.ema.access.OmmConsumerImpl - loggerMsg ClientName: LoginCallbackClient Severity: Warning Text: RDMLogin stream state was changed to suspect with status message username <not set> usernameType <not set> State: Open/Suspect/None - text: "" loggerMsgEnd 2019-06-03 10:16:12.528 [pool-15-thread-1] WARN com.thomsonreuters.ema.access.OmmConsumerImpl - loggerMsg ClientName: LoginCallbackClient Severity: Warning Text: RDMLogin stream state was changed to suspect with status message username <not set> usernameType <not set> State: Open/Suspect/None - text: "" loggerMsgEnd

2019-06-03 10:16:18.355 [pool-3-thread-1] INFO com.thomsonreuters.ema.access.OmmConsumerImpl - loggerMsg ClientName: ChannelCallbackClient Severity: Info Text: Received ChannelUp event on channel Channel_1 Instance Name Consumer_1_1 Component Version ads2.6.12.L1.linux.tis.rrg 64-bit loggerMsgEnd 2019-06-03 10:16:18.355 [pool-11-thread-1] INFO com.thomsonreuters.ema.access.OmmConsumerImpl - loggerMsg ClientName: ChannelCallbackClient Severity: Info Text: Received ChannelUp event on channel Channel_1 Instance Name Consumer_1_5 Component Version ads2.6.12.L1.linux.tis.rrg 64-bit loggerMsgEnd 2019-06-03 10:16:18.355 [pool-9-thread-1] INFO com.thomsonreuters.ema.access.OmmConsumerImpl - loggerMsg ClientName: ChannelCallbackClient Severity: Info Text: Received ChannelUp event on channel Channel_2 Instance Name Consumer_1_4 Component Version ads2.6.12.L1.linux.tis.rrg 64-bit loggerMsgEnd 2019-06-03 10:16:18.355 [pool-17-thread-1] INFO com.thomsonreuters.ema.access.OmmConsumerImpl - loggerMsg ClientName: ChannelCallbackClient Severity: Info Text: Received ChannelUp event on channel Channel_1 Instance Name Consumer_1_8 Component Version ads2.6.12.L1.linux.tis.rrg 64-bit loggerMsgEnd 2019-06-03 10:16:18.355 [pool-15-thread-1] INFO com.thomsonreuters.ema.access.OmmConsumerImpl - loggerMsg ClientName: ChannelCallbackClient Severity: Info Text: Received ChannelUp event on channel Channel_1 Instance Name Consumer_1_7 Component Version ads2.6.12.L1.linux.tis.rrg 64-bit loggerMsgEnd 2019-06-03 10:16:18.355 [pool-5-thread-1] INFO com.thomsonreuters.ema.access.OmmConsumerImpl - loggerMsg ClientName: ChannelCallbackClient Severity: Info Text: Received ChannelUp event on channel Channel_1 Instance Name Consumer_1_2 Component Version ads2.6.12.L1.linux.tis.rrg 64-bit loggerMsgEnd 2019-06-03 10:16:18.355 [pool-7-thread-1] INFO com.thomsonreuters.ema.access.OmmConsumerImpl - loggerMsg ClientName: ChannelCallbackClient Severity: Info Text: Received ChannelUp event on channel Channel_1 Instance Name Consumer_1_3 Component Version ads2.6.12.L1.linux.tis.rrg 64-bit loggerMsgEnd 2019-06-03 10:16:18.355 [pool-13-thread-1] INFO com.thomsonreuters.ema.access.OmmConsumerImpl - loggerMsg ClientName: ChannelCallbackClient Severity: Info Text: Received ChannelUp event on channel Channel_2 Instance Name Consumer_1_6 Component Version ads2.6.12.L1.linux.tis.rrg 64-bit loggerMsgEnd

elektron refinitiv-realtime elektron-sdk ema-api rrt elektron-message-api connection

Jun 03, 2019 at 05:35 AM

10 |1500

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

pimchaya.wongrukun01 Jun 03, 2019 at 11:21 PM

The client has submitted a case for this question. @jirapongse.phuriphanvichai is taking care of the case.

wasin.w Jun 18, 2019 at 01:35 AM

<AHS>

The case 07675319 has been closed. This is a resolution from @jirapongse.phuriphanvichai.

From the error text, I assume that the operating system is Windows and the error code could be WSAECONNABORTED (10053). Refer to the Windows Socket Error Codes page (https://docs.microsoft.com/en-us/windows/desktop/winsock/windows-sockets-error-codes-2), WSAECONNABORTED is “Software caused connection abort.”.

Therefore, it could be a network issue. To verify the problem, you can use a network protocol analyzer tool, such as Wireshark (https://www.wireshark.org/) to monitor data transmission time-out on the network and verify which side that cuts the connection.

The clinet can configure the reconnection time through the following configurations.

<ReconnectMaxDelay value="2000"/>
<ReconnectMinDelay value="1000"/>

I will ping Jirapongse to update this post.

Jirapongse Jun 25, 2019 at 02:25 AM

@blam

Hi,

Thank you for your participation in the forum.

Are any of the replies below satisfactory in resolving your query? If yes please click the 'Accept' text next to the most appropriate reply.

If you have already known an answer, please share your answer, and then accept it. This will guide all community members who have a similar question.

Otherwise please post again offering further insight into your question.

Thanks,

AHS

Answer 1 · 2019-06-03T08:39:40Z

umer.nalla

25.3k ●87 ●12 ●25

Hi @blam

The message does indeed mean that your application was disconnected by the server.

This could be because there was a problem with the server or your network. Please check with your market data to confirm if this was the case- they should be able to examine their ADS logs to check.

However, quite often this disconnect can also happen because your application is not processing the data from the server quickly enough.

The server can only buffer so much data before it has to disconnect the application once the buffer is full.

A common cause of this is when your application is spending too much time processing the data in the OnRefresh / OnUpdate callback handlers. These callbacks are executed on the API thread and the more time the API thread spends in the callback handlers, the less time it will have to read data from the server.

Ways of alleviating this situation include:

minimising the processing done in the callback handlers with the API thread, by offloading some processing to a seperate application level thread
splitting your instruments across more than one OmmConsumer instance i.e. horizontal scaling as demonstrated in example410

Jun 03, 2019 at 08:39 AM

10 |1500

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Answer 2 · 2019-06-03T09:31:19Z

nick.zincone

17.3k ●82 ●39 ●63

Hi @blam,

There are reconnect configuration parameters within the EMA config guides (reconnectMinDelay/reconnectMaxDelay) which you can configure.

ahs.png (82.0 KiB)

Jun 03, 2019 at 09:31 AM

10 |1500

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Answer 3 · 2019-06-11T02:15:25Z

Jirapongse

79.2k ●251 ●52 ●74

From the error text, I assume that the operating system is Windows and the error code could be WSAECONNABORTED (10053). Refer to the Windows Socket Error Codes page (https://docs.microsoft.com/en-us/windows/desktop/winsock/windows-sockets-error-codes-2), WSAECONNABORTED is “Software caused connection abort.”.

Therefore, it could be a network issue. To verify the problem, you can use a network protocol analyzer tool, such as Wireshark (https://www.wireshark.org/) to monitor data transmission time-out on the network and verify which side that cuts the connection.

You can configure the reconnection time through the following configurations.

You need to set the values of the configurations inside the consumer element. For example:

<Consumer>
         <Name value="Consumer_1"/>
         <Channel value="Channel_1"/>
         <Dictionary value="Dictionary_1"/>
         <XmlTraceToStdout value="0"/>
         <ReconnectMaxDelay value="2000"/>
         <ReconnectMinDelay value="1000"/>
</Consumer>

aborted.png (10.7 KiB)

config.png (160.0 KiB)

Jun 11, 2019 at 02:15 AM

10 |1500

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Q&A Forum

question

An established connection was aborted by the software in your host machine

3 Answers

Write an Answer

question

An established connection was aborted by the software in your host machine

3 Answers

Write an Answer

Related Questions