Discover Refinitiv
MyRefinitiv Refinitiv Perspectives Careers
Created with Sketch.
All APIs Questions & Answers  Register |  Login
Ask a question
  • Questions
  • Tags
  • Badges
  • Unanswered
Search:
  • Home /
  • Elektron /
  • EMA /
avatar image
Question by blam · Jun 03, 2019 at 05:35 AM · elektronrefinitiv-realtimeelektron-sdkrrtema-apielektron-message-apiconnection

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

People who like this

0 Show 0
Comment
10 |1500 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

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

3 Replies

  • Sort: 
avatar image
REFINITIV
Best Answer
Answer by umer.nalla · Jun 03, 2019 at 08:39 AM

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
Comment

People who like this

0 Show 0 · Share
10 |1500 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

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

avatar image
REFINITIV
Answer by nick.zincone · Jun 03, 2019 at 09:31 AM

Hi @blam,

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


ahs.png (82.0 KiB)
Comment

People who like this

0 Show 0 · Share
10 |1500 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

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

avatar image
REFINITIV
Answer by Jirapongse · Jun 11, 2019 at 02:15 AM

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)
Comment

People who like this

0 Show 0 · Share
10 |1500 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

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

Watch this question

Add to watch list
Add to your watch list to receive emailed updates for this question. Too many emails? Change your settings >
9 People are following this question.

Related Questions

Need to understand few extra details on disconnection issues.

Why the connection disconnected at 10:46 yesterday?

Monitor status of TREP connection

EMAJ: How to keep long connection to server in OMMConsumer?

We are getting connection status as down and timed-out while trying to connect to Reuter through Machine_Id,Port and IP through JAVA

  • Copyright
  • Cookie Policy
  • Privacy Statement
  • Terms of Use
  • Anonymous
  • Sign in
  • Create
  • Ask a question
  • Spaces
  • Alpha
  • App Studio
  • Block Chain
  • Bot Platform
  • Connected Risk APIs
  • DSS
  • Data Fusion
  • Data Model Discovery
  • Datastream
  • Eikon COM
  • Eikon Data APIs
  • Electronic Trading
    • Generic FIX
    • Local Bank Node API
    • Trading API
  • Elektron
    • EMA
    • ETA
    • WebSocket API
  • Intelligent Tagging
  • Legal One
  • Messenger Bot
  • Messenger Side by Side
  • ONESOURCE
    • Indirect Tax
  • Open Calais
  • Open PermID
    • Entity Search
  • Org ID
  • PAM
    • PAM - Logging
  • ProView
  • ProView Internal
  • Product Insight
  • Project Tracking
  • RDMS
  • Refinitiv Data Platform
    • Refinitiv Data Platform Libraries
  • Rose's Space
  • Screening
    • Qual-ID API
    • Screening Deployed
    • Screening Online
    • World-Check One
    • World-Check One Zero Footprint
  • Side by Side Integration API
  • TR Knowledge Graph
  • TREP APIs
    • CAT
    • DACS Station
    • Open DACS
    • RFA
    • UPA
  • TREP Infrastructure
  • TRKD
  • TRTH
  • Thomson One Smart
  • Transactions
    • REDI API
  • Velocity Analytics
  • Wealth Management Web Services
  • Workspace SDK
    • Element Framework
    • Grid
  • World-Check Data File
  • 中文论坛
  • Explore
  • Tags
  • Questions
  • Badges