Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Sun, 28 Apr 2024 10:38:36 +0000
Post From: CTS FIX connection issue.......
| [2013-08-24 01:12:14] |
| |
|
We have read through the additional comments in this thread. The reason for the CTS FIX simulation server outage was unknown to us. Only this morning did we learn that was due to a hardware problem. When we released support for FIX, it was our belief that generally everything was working fine and was acceptable for release. We did not knowingly release something which would have significant issues. As time went by, through our own additional testing and feedback from users we would see some issues . We would promptly work through those issues either on our side or report them over to CTS. Also, keep in mind, the initial release was a pre-release. Later that became the main release and believed everything was overall fine with the integration. There has been a lot of work done by the senior engineer (me) related to the downloading of historical data from CTS. This has now been made very reliable. After a technical review yesterday by the senior engineer, some order handling issues were discovered and we realized CTS really needs to make some changes in their FIX implementation order to provide more reliable trading integration with Sierra Chart. For our perspective, the CTS FIX implementation in some areas is nonstandard and impractical to work with. So we reported this to CTS yesterday and then later the simulation server went down. We had the impression that maybe they realized there is a lot of work they need to do and they wanted to take the server down for an extended time. We did not know. This was not a correct assumption. We did report the server outage to them. Anyway, we realized that we had to inform our users using the simulation server to use 997. This is all we could do. They fixed the hardware problem the server was back up this morning. It should be pointed out, that you always have available to use the T4 front end for trading and if you have a live account, there were no interruptions. The reason we do not want to place blame on CTS is because we really appreciate them developing the FIX interface and clearly they have put a lot of effort into that. There are several things we have communicated to them about their FIX implementation that we want to see changed though. We have communicated with them more this morning on some of these order related issues, and we have done some additional technical review . We are going to be releasing 1015 late this evening and from what we can tell, the order handling/Trading integration should generally be stable. It is not perfect, but there are no significant issues which should be observable. We do regard it as safe to trade with. We do see some odd behavior with server-side OCO, however we have disabled that and use Sierra Chart client-side OCO for now. Why do we use FIX rather than a proprietary API component: Http://www.sierrachart.com/index.php?l=doc/helpdetails76.html In regards to this: Something has now changed. Now, there is apparently no priority to fix this, no hurry for a fix, not even an eta on the fix. Just a, "not sure when it will be resolved". What does this mean? A couple of hours, days, weeks? That is very non-nonchalant response to someone that just lost hours of work.
We have no control over the CTS FIX server obviously. So this comment is not even relevant to us. Furthermore, you did not lose hours of work. Your current Chartbook still exists with all of your latest work, and when the server problem is resolved which it was by CTS you can just go back to the newest version of Sierra Chart and use your current Chartbook. While the situation was unfortunate, a few hours or even a half day interruption with a simulation server should not cause a significant hardship. Although none of us knew how long the interruption would be. Reasonably it should not have been very long (under a day). As we have said here, you still have access to the T4 front end for order entry. Is there some reason that ALL "backup" chartbooks don't work? Shouldn't any "backup", be just that? A usable backup?
All backup Chartbooks should work. If not we could test one for you. But we see no reason why there would be a problem. This does not mean that a particular backup will have all of your latest changes. However, they will open. FIX shouldn't have been implemented. That was SC's choice. We do not agree with this at all. The only reasonable choice was for us to use a direct socket integration method to CTS. API components are not acceptable to us. Our position is made very very clear in help topic 76. These have been the source of major technical problems for us which we have no control over.There is nothing more important then each side, the client and the server (trading service) to interface to each others systems by using a common protocol like FIX or GSP. This is absolutely essential and creates the very best working relationship. We are way ahead of everyone else by making this a priority and working towards this goal. Superior engineering is our highest objective. In regards to all of this Chartbook rebuilding. We will see what we can do to maintain a more recent backup. However, probably some of you may have been too quick on this. Being that the server came back up this morning. 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: 2013-08-24 09:13:28
|