Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Sun, 28 Apr 2024 15:21:54 +0000
Notice: Transact Websocket Connectivity Issue
View Count: 7696
| [2019-08-15 14:54:28] |
| |
|
If you are using Sierra Chart with Transact versions 1942 or later which uses the websocket connection and Sierra Chart is not able to maintain the connection to Transact, then just simply restart Sierra Chart. We are forcing an update to version 1975. What will happen after the restart is the installer will be downloaded and then you will get a prompt to run the installer. Just go through the installation process to install 1975. And then run Sierra Chart again. We have implemented a patch for the issue. The issue is not entirely clear but it relates to extension bits on the websocket protocol. You can also update to the current version with Help >> Download Current Version. If you have any further questions just post here. 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: 2019-08-15 14:57:52
|
| [2019-08-15 16:56:31] |
| User90125 - Posts: 715 |
|
Any idea when the legacy TA bridge connection will be available for charting AND trading, as promised recently? We are going to work on restoring the old Transact bridge program this evening. So that will be out before morning.
Just tried to live TRADE thru v1975. No bueno. And no legacy TA connection either. Just the Transact WS (websocket) instead. Order Error - Trading connection is disconnected. Internal Order ID: 8. Service Order ID: (none). Symbol: MNQU9. Account: 90125 | 2019-08-15 12:42:19.009
Please advise when you can. |
| [2019-08-15 19:47:05] |
| |
|
Restoring the old Transact bridge program is more involved than we thought. We expect to have it done by tomorrow.
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 |
| [2019-08-17 23:36:26] |
| User388767 - Posts: 10 |
|
Just updated to the latest version - I believe 1975 - but still unable to connect to the data feed for this week's trading review. Had the same issue last weekend while trying to review the week's trading (repeated attempts to connect and the WebSocket thing). I believed you got me going again rather quickly -- much appreciated. Anything you can do to help me along again today would be much appreciated or perhaps you're working on the system.
|
| [2019-08-18 00:14:53] |
| |
|
In regards to post #4 you are using CQG. The CQG server is down. This has nothing to do with Sierra Chart. But this should not cause you any problem. Just select File >> Disconnect to prevent Sierra Chart from connecting. 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: 2019-08-18 04:04:43
|
| [2019-08-18 11:02:16] |
| User657944 - Posts: 173 |
|
Just FYI I tried to upgrade to 1975 as a Transact user and in SIM live mode the websocket is working and also I was surprised to find the DOM available now (they told no chance before september) so on monday I will try to see what will happen on live mode.
|
| [2019-08-18 11:35:14] |
| |
|
The Trading websocket API from Transact is not available now. That we know for sure.
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: 2019-08-18 11:35:21
|
| [2019-08-18 12:34:42] |
| User657944 - Posts: 173 |
|
I beleive You was just to notify the community that there's something new that is working on since on other posts I yet saw people with connection issue with latest versions.
|
| [2019-08-18 17:57:03] |
| User90125 - Posts: 715 |
|
Hopefully SC will have it ready for trading this week. Latest prerelease I tried on my dev box (v1976) didn't have the legacy TA connection at all.
|
| [2019-08-20 08:20:50] |
| User90125 - Posts: 715 |
|
Uploaded v1977. Still no legacy TA bridge connection. Any update on when this may be available for use?
|
| [2019-08-20 08:25:39] |
| |
|
We have decided for the time being not to bring the bridge back. We put a lot of work into this websocket connection implemented it well and properly and we continue to maintain that. This is the new interface that Transact is providing and they are responsible for taking care of any problems with it. We will also continue to enhance it, including eventually processing it on a background thread. As we started to go through bringing back the bridge back, there are a lot of little pieces and implementation details to it. It was not simple to do. Just stay on version 1941 for now. Here are the rollback procedures: Software Download: Software Rollback Procedure One thing we have realized is that we have been far too accommodating on issues like this over the years. We have to hold the line here. And we are going to hold the line here. Our decision on this is final. If users want to leave over this matter, then that is going to be the end result. We are holding the line on 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: 2019-08-20 08:33:51
|
| [2019-08-20 08:55:50] |
| User90125 - Posts: 715 |
|
Thank you for the update. I'd like to use a DTC implementation with 1941 (TA bridge) as the source, and newer versions (1975+) as the destination, in a new instance. Based on what I read on the updated documentation page, I should think this would be the only feasible implementation, going forward. Using DTC Server for Data and Trading in Another Sierra Chart Instance: Using DTC Server for Data and Trading in Another Sierra Chart Instance Any pointers or comments would be appreciated. |
| [2019-08-20 15:27:30] |
| |
|
We will get back to you on this. But as we were troubleshooting a problem where users were getting disconnected we think the problem is that there are fragmented frames being provided. We have not encountered these before an websocket connection so we need to add support for that. We will have fragmented frame support ready today. 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: 2019-08-20 15:27:44
|
| [2019-08-20 16:24:28] |
| |
|
We have released version 1978 with a temporary solution to disconnections when using the Transact websocket data feed. We will have a full and proper solution out later today. 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 |
| [2019-08-21 01:15:06] |
| Meklon - Posts: 217 |
|
Well....I have been on version 1967 for several weeks and until yesterday it was functioning. Today I am able to connect to Transact but when placing orders on Sierra Chart they are not showing up on the Infinity DOM and after 5-7 seconds disappear from the chart with the following error message in the log: Requesting order status for non-responsive order. | Symbol: ESU9 | TradeAccount: [Sim]******* | InternalOrderID: 48424 | Current Status: Order Sent | 2019-08-20 21:04:56.721 * Trade Order Error - Order timed-out waiting for response from service/exchange server. Internal Order ID: 48424. Service Order ID: (none). Symbol: ESU9. Account: [Sim]******8 | 2019-08-20 21:05:26.711 * I have tried to upgrade to the latest version 1978 but no effect - same problem. Orders are placed on the chart not showing in the DOM and not going through. After few seconds they disappear. This is a MAJOR outage, impacting trading. Please advise |
| [2019-08-21 06:43:00] |
| |
|
This has been answered here: Orders placed From Sierra Chart Not Appearing On TransAct DOM and Not Routed for Executio Really the orders should be rejected outright and we are not sure why that is not the case. 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 |
| [2019-08-21 10:27:54] |
| User90125 - Posts: 715 |
|
Any update on the question posed in post #12? I'd like to use a DTC implementation with 1941 (TA bridge) as the source, and newer versions (1975+) as the destination, in a new instance.
Based on what I read on the updated documentation page, I should think this would be the only feasible implementation, going forward. Using DTC Server for Data and Trading in Another Sierra Chart Instance: Using DTC Server for Data and Trading in Another Sierra Chart Instance Any pointers or comments would be appreciated. |
| [2019-08-21 18:12:18] |
| |
|
You can use a configuration that does not support trading but allows you to share market data between instances and this is documented here: https://www.sierrachart.com/index.php?page=doc/MultipleServices.html#AccessingMarketDataFromOtherInstancesOfSierra%20Chart This only allows the sharing of market data between Sierra Chart instances. But it will work properly for market data. You need to have two separate installations of Sierra Chart and login independently to them. Not using File >> New Instance. For this to work properly you will need a direct account: Direct Sierra Chart Account If you want to have trading support, you would need to use the method here (same as what you linked to above): Using DTC Server for Data and Trading in Another Sierra Chart Instance: Using DTC Server for Data and Trading in Another Sierra Chart Instance However, this is going to require a direct account so you can login independently to each installation not using File >> New Instance. And then each installation can be a different version. 1941 for one and then the newer version for the client instance. 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: 2019-08-21 18:18:15
|
| [2019-08-21 18:14:26] |
| |
|
We are revising the above post. Just give us a couple of minutes. What we previously said was not technically correct.
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: 2019-08-21 18:16:38
|
| [2019-08-21 18:19:05] |
| |
|
Post 18 has been updated and is now technically correct and will give you what you need. Let us know if you need any help with a direct account. 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 |
| [2019-08-22 11:22:44] |
| |
|
Prerelease version 1979 has been released and supports fragmented websocket messages which should solve some disconnection issues we have seen.
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 |
| [2019-08-23 01:03:30] |
| abrown8703 - Posts: 64 |
|
Version 1979 disconnects frequently. Going back to version 1941, which seems to be the last stable TransAct version that is stable for now.
|
| [2019-08-23 03:05:24] |
| |
|
Actually the reason for the disconnections is because the orders connection is disconnecting. We have notice that ourselves. That is not what we were solving by adding support for websocket frame fragmentation. We will have to just add an option to disable the use of the Transact orders connection altogether. 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 |
| [2019-08-23 03:21:45] |
| Meklon - Posts: 217 |
|
What I can't understand is how is this possible for Sierra to release a MAJOR new functionality (Web Socket Interface) without adequately testing it with a counterparty (Transact) and have so many traders badly impacted, practically causing them to either seize trading entirely because they no longer able to place orders to Transact from the charts or to be severely limited in their trading (rolling back to Version 1941) because many custom studies compiled on newer versions of Sierra no longer working? This is by far the biggest failed rollout of new functionality I have seen and quite frankly I would expect more professional approach from Sierra on this subject. Why not simply integrate the old Transact Bridge connectivity option into latest Sierra version until this situation is resolved? |
| [2019-08-23 04:31:08] |
| |
|
What I can't understand is how is this possible for Sierra to release a MAJOR new functionality (Web Socket Interface) without adequately testing it with a counterparty (Transact) and have so many traders badly impacted, It was well tested. There are two basic issues. The two basic issues we have seen, is authorization problems on the Transact side. That is not something we have any control over or would have been aware of ahead of time and is easily resolved by Transact.And we also did not know the users were not able to use the Trading connection. It is certainly usable in the test environment, and we expected that Transact would make this available shortly. We did not realize it would be going on for weeks. And this most recent issue with the disconnection of the orders connection, is something that really we have just noticed in the last couple of days ourselves. We will have a solution implemented before morning. At best this is a minor non-impacting issue. And it is also something that that Transact could resolve on their side as well. They need to make the connection stable or just not allow the connection. 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: 2019-08-23 05:45:51
|
To post a message in this thread, you need to log in with your Sierra Chart account: