Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Sat, 04 May 2024 01:08:10 +0000
a couple of issues with the DTC server
View Count: 1698
| [2017-02-05 02:43:04] |
| user8888 - Posts: 159 |
|
Hello. I've been trying to setup a 2nd instance in my trading computer. (1). They both, connect fine until I load the chartbook. Then disconects the DTC server from the data feed and keeps connecting and disconnecting over and over. In the message log appears this message: =========================================================================================================== DTCServer (4) | Encryption stream error encountered. error:140E0197:SSL routines:SSL_shutdown:shutdown while in init; error:140E0197:SSL routines:SSL_shutdown:shutdown while in init | 2017-02-04 02:18:59 DTCServer (4) | Encryption stream error encountered. error:140E0197:SSL routines:SSL_shutdown:shutdown while in init; error:140E0197:SSL routines:SSL_shutdown:shutdown while in init | 2017-02-04 02:18:59 DTCServer (4) | Shutdown started. Waiting for graceful close. | 2017-02-04 02:18:59 and CQG WebAPI websocket (2) | Encryption stream error encountered. error:140E0197:SSL routines:SSL_shutdown:shutdown while in init | 2017-02-04 02:19:01 CQG WebAPI websocket (2) | Encryption stream error encountered. error:140E0197:SSL routines:SSL_shutdown:shutdown while in init | 2017-02-04 02:19:01 CQG WebAPI | Network socket for websocket has been closed by remote side. | 2017-02-04 02:19:01 CQG WebAPI websocket (2) | Shutdown started. Waiting for graceful close. | 2017-02-04 02:19:01 CQG FIX Trading | Websocket closed. | 2017-02-04 02:19:01 Connection to the external service has been lost. | 2017-02-04 02:19:01 CQG FIX: DisconnectFIX called. | 2017-02-04 02:19:01 CQG FIX: Sending a Logout message. | 2017-02-04 02:19:01 CQG FIX Trading | Disconnected. | 2017-02-04 02:19:01 Will reconnect to the server in 3.0 seconds. CQG WebAPI websocket (2) | Received socket Close event | 2017-02-04 02:19:01 CQG WebAPI websocket (2) | Closed. | 2017-02-04 02:19:01 CQG FIX: Received a Logout message. Text = NormalLogoutInitiatedByCounterparty | 2017-02-04 02:19:01 CQG FIX: Disconnected. | 2017-02-04 02:19:01 and more socket (12) | Encryption stream error encountered. error:140E0197:SSL routines:SSL_shutdown:shutdown while in init | 2017-02-04 02:19:30 CQG FIX: Socket connection was closed without any logout messages sent or received. | 2017-02-04 02:19:30 socket (12) | Shutdown started. Waiting for graceful close. | 2017-02-04 02:19:30 CQG FIX: Disconnected. | 2017-02-04 02:19:30 Connection to the external service has been lost. | 2017-02-04 02:19:30 CQG FIX Trading | Sending Web API Logoff message. | 2017-02-04 02:19:30 DTCServer (20) | Encryption stream error encountered. error:140E0197:SSL routines:SSL_shutdown:shutdown while in init; error:140E0197:SSL routines:SSL_shutdown:shutdown while in init; error:140E0197:SSL routines:SSL_shutdown:shutdown while in init | 2017-02-04 02:19:45 DTCServer (20) | Shutdown started. Waiting for graceful close. | 2017-02-04 02:19:45 DTCServer (20) | Received socket Close event | 2017-02-04 02:19:45 DTCServer (20) | Closed. | 2017-02-04 02:19:45 =========================================================================================================== Since the message says something about the 'encription', I've tried with and without the TLS enabled. Same result. I've try it as well with my laptop as the DTC client. Same result. (2). If I setup the DTC Server to allow only IPs comming from the same subnet, the server rejects the client/laptop. I need to set it up with 'Allow any IP'. Then goes ok. being the host: 192.168.1.148 and the laptop: 192.168.1.166 ... Aren't they in the same subnet? (they are both connected to the same bridge/router/DHCPserver) (3). Months ago when I first tried the DTC server/client funcionality (great thing BTW), I noticed that the commisions that I entered by hand in certain symbols, did not were 'transmited' to the DTC client. I tried 'resetting' the symbol list and ask it again from the DTC Client to the Server, with the same result. I haven't had the chance to test if this behavior still exists since I'm actually unable to even load a chartbook. Am I doing something wrong? Could you help? Thank you Date Time Of Last Edit: 2017-02-05 03:42:51
|
| [2017-02-05 03:53:16] |
| |
|
CQG WebAPI websocket (2) | Encryption stream error encountered. error:140E0197:SSL routines:SSL_shutdown:shutdown while in init | 2017-02-04 02:19:01 This is very unusual. We want you to update to Prerelease 1514 with Help >> Download Prerelease and see if you have any further trouble connecting to CQG. In regards to the DTC server and client, make sure you do not use TLS on each side. You need to disable that on both sides. 3. Months ago when I first tried the DTC server/client funcionality (great thing BTW), I noticed that the commisions that I entered by hand in certain symbols, did not were 'transmited' to the DTC client.
The Symbol Settings will not transfer between a DTC Server and Client unless you are using File >> New Instance and have enabled Global Settings >> Symbol Settings >>Use Symbol Settings in New Instances When Started. 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: 2017-02-05 04:03:37
|
| [2017-02-05 07:38:06] |
| user8888 - Posts: 159 |
|
updated to 1514 and now, it works! Thank you for such a fast fix! However there is still one ugly message in the message log of the DTC server (does not appear in the message log of the DTC client) this one: ===================================================================== Socket (563) | Creating socket. | 2017-02-05 07:33:14 Error posting message in c_AsyncWindow::PostMessage. Windows error code 1400: El identificador de la ventana no es válido. | 2017-02-05 07:33:14 * HD Server | Timed out waiting for logon request. | 2017-02-05 07:33:25 Socket (563) | 296 bytes remaining in receive buffer when socket closed. | 2017-02-05 07:33:25 HD Server | Server thread ending. Socket closed. | 2017-02-05 07:33:25 ===================================================================== Althought does not disconnects and reconnects again as previously. Some data got badly downloaded. Re-downloading them solved it. one question unrelated: Could you please create the "Candle Price Volume Bars" hollow variant? Thanks so much! Date Time Of Last Edit: 2017-02-05 07:46:03
|
| [2017-02-05 09:19:34] |
| |
|
being the host: 192.168.1.148 and the laptop: 192.168.1.166 ... Aren't they in the same subnet? (they are both connected to the same bridge/router/DHCPserver)
Yes but you need to look at how the IP is reported to Sierra Chart. You will see the incoming IP in the Message Log in the DTC Server instance.In regards to post #3, do not use 1514. Apparently there is some problem we need to look into or there is a system problem on your side. Do not ask us about any feature requests. That is the least of our concern at this point in time. And they should be in another thread 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 |
| [2017-02-05 09:45:59] |
| |
|
We have released version 1515 which we hope will resolve the problems. If you have some time give that a try and let us know if there are any further issues. We do apologize for the issues. We suspect they are within open SSL and Google protocol buffers neither of which we developed. We went back to the prior version of Google protocol buffers and we think we have the open SSL issues resolved. 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 |
To post a message in this thread, you need to log in with your Sierra Chart account: