Support Board
Date/Time: Wed, 27 Nov 2024 00:24:22 +0000
Windows error code 10054: Connection reset by peer.
View Count: 5692
| [2014-07-09 15:53:24] |
| T44 - Posts: 363 |
|
This error has been occurring several times today. CTS FIX socket (476) - Closed. Windows error code 10054: Connection reset by peer. | 2014-07-09 11:51:23 CTS FIX socket (476) - SSL shutdown indicates not able to send 'close notify'. | 2014-07-09 11:51:23 CTS FIX socket (476) - SSL has been shut down. | 2014-07-09 11:51:23 CTS FIX socket (476) - SSL object has been freed. SSL state is now disconnected. | 2014-07-09 11:51:23 CTS FIX socket (476) - Shutdown error. Unknown Windows error code 10058. | 2014-07-09 11:51:23 CTS FIX socket (476) - Shutdown and closed. | 2014-07-09 11:51:23 CTS FIX: Socket connection was closed without any logout messages sent or received. | 2014-07-09 11:51:23 Connection to the external service has been lost. | 2014-07-09 11:51:23 CTS FIX: Disconnected. | 2014-07-09 11:51:23 Will reconnect to the server in 3.0 seconds Select File >> Disconnect to prevent further connection attempts. | 2014-07-09 11:51:23 |
| [2014-07-09 15:53:54] |
| T44 - Posts: 363 |
|
Also CTS FIX Historical Data socket (492) - Closed. No error. | 2014-07-09 11:52:42 CTS FIX Historical Data socket (492) - SSL shutdown indicates not able to send 'close notify'. | 2014-07-09 11:52:42 CTS FIX Historical Data socket (492) - SSL has been shut down. | 2014-07-09 11:52:42 CTS FIX Historical Data socket (492) - SSL object has been freed. SSL state is now disconnected. | 2014-07-09 11:52:42 CTS FIX Historical Data socket (492) - Shutdown and closed. | 2014-07-09 11:52:42 CTS FIX Historical Data: Socket connection was closed without any logout messages sent or received. | 2014-07-09 11:52:42 CTS FIX Historical Data: Disconnected. | 2014-07-09 11:52:42 |
| [2014-07-09 16:02:16] |
| T44 - Posts: 363 |
|
CTS FIX Historical Data: Received a Logout message. Text = Chart Data Timeout. No valid chart data requests were received within the chart data interval of 60 seconds | 2014-07-09 12:01:44
CTS FIX Historical Data: Sending a Logout message. Text = Received Logout message. | 2014-07-09 12:01:44 CTS FIX Historical Data socket (216) - SSL shutdown indicates not able to send 'close notify'. | 2014-07-09 12:01:44 CTS FIX Historical Data socket (216) - SSL has been shut down. | 2014-07-09 12:01:44 CTS FIX Historical Data socket (216) - SSL object has been freed. SSL state is now disconnected. | 2014-07-09 12:01:44 CTS FIX Historical Data socket (216) - Shutdown and closed. | 2014-07-09 12:01:44 CTS FIX Historical Data: Logged out and disconnected. | 2014-07-09 12:01:44 CTS FIX Historical Data: Disconnected. | 2014-07-09 12:01:44 |
| [2014-07-09 16:19:54] |
| |
|
It is not unusual for the remote server to close the CTS FIX Historical Data connection. That is expected. This is unusual: CTS FIX socket (476) - Closed. Windows error code 10054: Connection reset by peer. | 2014-07-09 11:51:23 Are you still noticing the problem currently? Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2014-07-09 16:20:47
|
| [2014-07-09 16:39:13] |
| T44 - Posts: 363 |
|
More info: CTS FIX Historical Data: Received a Logout message. Text = Chart Data Timeout. No valid chart data requests were received within the chart data interval of 60 seconds | 2014-07-09 12:38:39
CTS FIX Historical Data: Sending a Logout message. Text = Received Logout message. | 2014-07-09 12:38:39 CTS FIX Historical Data socket (216) - SSL shutdown indicates not able to send 'close notify'. | 2014-07-09 12:38:39 CTS FIX Historical Data socket (216) - SSL has been shut down. | 2014-07-09 12:38:39 CTS FIX Historical Data socket (216) - SSL object has been freed. SSL state is now disconnected. | 2014-07-09 12:38:39 CTS FIX Historical Data socket (216) - Shutdown and closed. | 2014-07-09 12:38:39 CTS FIX Historical Data: Logged out and disconnected. | 2014-07-09 12:38:39 CTS FIX Historical Data: Disconnected. | 2014-07-09 12:38:39 ååÿ |
| [2014-07-09 17:11:57] |
| |
|
This is expected: CTS FIX Historical Data: Received a Logout message. Text = Chart Data Timeout. No valid chart data requests were received within the chart data interval of 60 seconds | 2014-07-09 12:38:39
CTS will close the historical data connection if it is not being used. So there is nothing unusual about this. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2014-07-10 02:24:24
|
| [2014-07-09 17:46:57] |
| T44 - Posts: 363 |
|
What is unusual is that I am subscribed to real time symbols in intraday charts and the data from these is not coming through, then around 30 seconds to a minute later I get the disconnection messages, then Sierra tries to reconnect. Am still experiencing the issue, any instructions? |
| [2014-07-09 17:52:26] |
| T44 - Posts: 363 |
|
This is occurring while I am subscribed to real time market data updates for several symbols. The data feed was lost. There was no activity for at least 60.0 seconds. | 2014-07-09 13:51:27 Connection to the external service has been lost. | 2014-07-09 13:51:27 CTS FIX: Sending a Logout message. | 2014-07-09 13:51:27 CTS FIX: Disconnected. | 2014-07-09 13:51:27 Will reconnect to the server in 3.0 seconds Select File >> Disconnect to prevent further connection attempts. | 2014-07-09 13:51:27 CTS FIX - Connecting to CTS Live server fix.t4login.com:10443 | 2014-07-09 13:51:30 CTS FIX - Firm: Dorman | 2014-07-09 13:51:30 CTS FIX: Unable to connect. The last connection is still in the process of logging out. | 2014-07-09 13:51:30 Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. | 2014-07-09 13:51:30 To prevent further connection attempts, select 'File >> Disconnect'. | 2014-07-09 13:51:30 CTS FIX: Disconnected. | 2014-07-09 13:51:30 Will reconnect to the server in 3.0 seconds Select File >> Disconnect to prevent further connection attempts. | 2014-07-09 13:51:30 CTS FIX: Waiting for Logout response timed out. Closing the socket now. | 2014-07-09 13:51:31 CTS FIX socket (456) - SSL shutdown indicates not able to send 'close notify'. | 2014-07-09 13:51:31 CTS FIX socket (456) - SSL has been shut down. | 2014-07-09 13:51:31 CTS FIX socket (456) - SSL object has been freed. SSL state is now disconnected. | 2014-07-09 13:51:31 CTS FIX socket (456) - Shutdown and closed. | 2014-07-09 13:51:31 CTS FIX: Socket closed without completing the logout sequence. | 2014-07-09 13:51:31 CTS FIX - Connecting to CTS Live server fix.t4login.com:10443 | 2014-07-09 13:51:33 CTS FIX - Firm: Dorman | 2014-07-09 13:51:33 CTS FIX socket (0) - Resolved address fix.t4login.com to IP 74.201.6.106 | 2014-07-09 13:51:33 CTS FIX socket (456) - Connected. | 2014-07-09 13:51:33 CTS FIX socket (456) - Starting SSL connection. | 2014-07-09 13:51:33 CTS FIX socket (456) - SSL connection established. | 2014-07-09 13:51:34 CTS FIX: Sending the Logon message. | 2014-07-09 13:51:34 CTS FIX: Connected to data and trade server. FIX version: 4.3.7.0 | 2014-07-09 13:51:34 CTS T4 FIX - Starting real-time market data updates for: 6E.20140900.CME_Fo. ID: 1 | 2014-07-09 13:51:34 CTS T4 FIX - Starting real-time market data updates for: GC.20140800.CME_CO. ID: 2 | 2014-07-09 13:51:34 CTS T4 FIX - Starting real-time market data updates for: NG.20140800.CME_NY. ID: 3 | 2014-07-09 13:51:34 CTS T4 FIX - Starting real-time market data updates for: CL.20140800.CME_NY. ID: 4 | 2014-07-09 13:51:34 CTS T4 FIX - Starting real-time market data updates for: ES.20140900.CME_Eq. ID: 5 | 2014-07-09 13:51:34 CTS T4 FIX - Starting real-time market data updates for: YM.20140900.CME_E. ID: 6 | 2014-07-09 13:51:34 CTS T4 FIX - Starting real-time market data updates for: NQ.20140900.CME_Eq. ID: 7 | 2014-07-09 13:51:34 CTS T4 FIX - Starting real-time market data updates for: TF.20140900.ICE_IN. ID: 8 | 2014-07-09 13:51:34 HD Request # 20 - Downloading Intraday chart data for 6E.20140900.CME_Fo to the file 6E.20140900.CME_Fo.scid. Service: cts | 2014-07-09 13:51:34 HD Request # 20 - Download start Date-Time: 2014-07-09 13:50:10.0 | 2014-07-09 13:51:34 CTS FIX Historical Data - Connecting to Historical data server fix-chart.t4login.com:10443 | 2014-07-09 13:51:34 CTS FIX: Received Account List collateral report. | 2014-07-09 13:51:35 CTS FIX: Subscribing to account: 13* | 2014-07-09 13:51:35 CTS FIX Historical Data socket (0) - Resolved address fix-chart.t4login.com to IP 208.116.215.116 | 2014-07-09 13:51:35 CTS T4 FIX: Sending security definition request for symbol 6E.20140900.CME_Fo | 2014-07-09 13:51:35 CTS T4 FIX: Received matching security definition for symbol 6E.20140900.CME_Fo. Subscribing to data. | 2014-07-09 13:51:35 CTS T4 FIX: Received 1 security definitions for underlying symbol 6E | 2014-07-09 13:51:35 CTS FIX Historical Data socket (468) - Connected. | 2014-07-09 13:51:35 CTS FIX Historical Data socket (468) - Starting SSL connection. | 2014-07-09 13:51:35 CTS FIX Historical Data socket (468) - SSL connection established. | 2014-07-09 13:51:35 CTS FIX: Received Account Update collateral report. | 2014-07-09 13:51:36 CTS FIX Historical Data: Sending the Logon message. | 2014-07-09 13:51:36 CTS FIX Historical Data: Connected to Historical data server. | 2014-07-09 13:51:36 Date Time Of Last Edit: 2014-07-09 19:13:58
|
| [2014-07-09 19:04:05] |
| T44 - Posts: 363 |
|
CTS FIX socket (476) - Closed. Windows error code 10054: Connection reset by peer. | 2014-07-09 14:56:44
CTS FIX socket (476) - SSL shutdown indicates not able to send 'close notify'. | 2014-07-09 14:56:44 CTS FIX socket (476) - SSL has been shut down. | 2014-07-09 14:56:44 CTS FIX socket (476) - SSL object has been freed. SSL state is now disconnected. | 2014-07-09 14:56:44 CTS FIX socket (476) - Shutdown error. Unknown Windows error code 10058. | 2014-07-09 14:56:44 CTS FIX socket (476) - Shutdown and closed. | 2014-07-09 14:56:44 CTS FIX: Socket connection was closed without any logout messages sent or received. | 2014-07-09 14:56:44 Connection to the external service has been lost. | 2014-07-09 14:56:44 CTS FIX: Disconnected. | 2014-07-09 14:56:44 Will reconnect to the server in 3.0 seconds Select File >> Disconnect to prevent further connection attempts. | 2014-07-09 14:56:44 |
| [2014-07-10 00:16:09] |
| |
|
We need to contact CTS about this. What we need you to do is press the Send For Analysis button on the Sierra Chart Message Log. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2014-07-10 02:26:37] |
| |
|
One thing we want you to check is Global Settings >>Data/Trade Service Settings >> Other Settings >> Data Throughput and Buffering. What is this set to? Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2014-07-10 08:24:45] |
| T44 - Posts: 363 |
|
One thing we want you to check is Global Settings >>Data/Trade Service Settings >> Other Settings >> Data Throughput and Buffering. What is this set to? Smart trade. I have sent message log as requested. Date Time Of Last Edit: 2014-07-10 08:29:24
|
| [2014-07-10 11:51:43] |
| T44 - Posts: 363 |
|
Still occurring on SC 1158. These random disconnects makes the platform basically unusable. Will have to ask my FCM to switch me over to TT backend if this cannot be fixed quickly. CTS FIX socket (472) - Closed. Unknown Windows error code 10054. | 2014-07-10 07:49:39 CTS FIX socket (472) - SSL shutdown indicates not able to send 'close notify'. | 2014-07-10 07:49:39 CTS FIX socket (472) - SSL has been shut down. | 2014-07-10 07:49:39 CTS FIX socket (472) - SSL object has been freed. SSL state is now disconnected. | 2014-07-10 07:49:39 CTS FIX socket (472) - Shutdown error. Unknown Windows error code 10058. | 2014-07-10 07:49:39 CTS FIX socket (472) - Shutdown and closed. | 2014-07-10 07:49:39 CTS FIX: Socket connection was closed without any logout messages sent or received. | 2014-07-10 07:49:39 Connection to the external service has been lost. | 2014-07-10 07:49:39 CTS FIX: Disconnected. | 2014-07-10 07:49:39 Will reconnect to the server in 3.0 seconds Select File >> Disconnect to prevent further connection attempts. | 2014-07-10 07:49:39 CTS FIX socket (472) - Closed. Unknown Windows error code 10054. | 2014-07-10 07:54:59
CTS FIX socket (472) - SSL shutdown indicates not able to send 'close notify'. | 2014-07-10 07:54:59 CTS FIX socket (472) - SSL has been shut down. | 2014-07-10 07:54:59 CTS FIX socket (472) - SSL object has been freed. SSL state is now disconnected. | 2014-07-10 07:54:59 CTS FIX socket (472) - Shutdown error. Unknown Windows error code 10058. | 2014-07-10 07:54:59 CTS FIX socket (472) - Shutdown and closed. | 2014-07-10 07:54:59 CTS FIX: Socket connection was closed without any logout messages sent or received. | 2014-07-10 07:54:59 Connection to the external service has been lost. | 2014-07-10 07:54:59 CTS FIX: Disconnected. | 2014-07-10 07:54:59 Will reconnect to the server in 3.0 seconds Select File >> Disconnect to prevent further connection attempts. | 2014-07-10 07:54:59 Date Time Of Last Edit: 2014-07-10 11:59:30
|
| [2014-07-10 16:58:28] |
| |
|
We apologize for this telling you this later on, but really it be best if you contact CTS about this. We can tell that you know what you are doing. Usually the reason we get involved in this, is for less experienced users. You can contact CTS here: http://www.ctsfutures.com/contact.aspx You will need to let them know your T4 username and whether you are connecting to the Live or Simulation server. And give them the time and time zone of the time you are losing the connection. By contacting CTS directly you will get the fastest response. Based upon the Message Log, we just realized you are using a non-Windows operating system. Please do not contact CTS about this. Use Windows. While you may not like Windows, and neither do we, for the greatest reliability and stability, use Windows. CTS is not going to be happy to be contacted about a problem which may reside on your side. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2014-07-10 16:59:31
|
| [2014-07-10 20:07:51] |
| T44 - Posts: 363 |
|
Non windows operating system: suspected this problem was caused by Wine updating to 1.7.21. Did a clean build using 1.7.19 and 1.7.20: same issue exists. CTS support: agree that I need to reproduce the problem under Windows before contacting them. Never sure whether it could be a CTS issue or a Sierra Chart issue, and as you have the more helpful support I contact you first. CTS tend to tell me that "our FIX connection is in Beta" and therefore may have issues, and leave it at that (or mention that their API is the preferred interface, which I know SC no longer offer for sensible development reasons). You did mention native Linux support some time in 2014 - any estimates? This would of course be extremely useful. I'll report back to the thread if I can reproduce this in Windows and also if I get any useful information from CTS. Thanks. |
| [2014-07-11 00:02:40] |
| |
|
We do not know the exact source of the problem. It could be on the CTS side, could be on the Wine side, or the network connectivity somewhere between the client and the server. It definitely is not an issue within Sierra Chart. The network communication component which is used for the connection to CTS is the very same code used on our server to serve data. It is very reliable. The CTS FIX connection is not a beta any longer. We are not going to be having native Linux support in 2014. But the project is gradually being worked on. It is probably not going to be until mid-2015. Once you reproduce the problem in Windows, then you have a more solid position going to CTS. This is the network error being encountered: An existing connection was forcibly closed by the remote host. (10054) The question is why is the CTS side doing that. I guess you could go ahead and ask them anyway. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2014-07-11 00:03:04
|
To post a message in this thread, you need to log in with your Sierra Chart account: