Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Sat, 27 Apr 2024 07:07:28 +0000
Post From: Rithmic Data Connection Failure
| [2018-06-09 10:59:20] |
| |
|
Rithmic told us this after the outage: Well, our service is now restored. Please be aware that users with up to date config were not affected by our outage.
We strongly recommend that you release the correct configuration as soon as possible. The current configs were released in June of 2016. By my reckoning your config dates back to 2012. Let me know if I can provide any assistance. Attached is the folder that Rithmic has set up for us, to access their API software and the connection parameters. Notice the enormous amount of connection parameters. Also understand that Sierra Chart does not directly connect to Rithmic. It is Rithmic's own software that does the connection. So if there is a connection problem, only Rithmic can have an explanation as to what the issue is. We simply cannot. The Rithmic software that you are all running, contains the connection parameters in the red highlighted file in the attachment. Notice the date is 21-Jun-2016 . So we are not using old parameters and the claim that the parameters we are using are from 2012 is incorrect and we do not know how they are making a mistake with this. Now we also see two other Chicago area sets of parameters just above in the list. We do not recall seeing those before. So that looks as though they were recently added. We have accessed this folder about three times in the last couple of years and we do periodically update the connection parameters. And as we said, the parameters match the red highlighted file exactly. Therefore, what can we determine from all of this? The connectivity problem is with Rithmic and they have to explain what has happened. We have no idea. Perhaps the API software itself has to be updated. The reason we do not do that is there always complications when updating API components in general. It is something to be avoided. And as a matter of policy we no longer support those: Sierra Chart Does not Support External Service API Components But we do continue to maintain the existing support. At this point, we see that no action needs to be taken on our part because we have no idea what to do. Rithmic needs to explain the problem. Their current explanation does not fit. ---- 2018-10-12 update: We have tried to update the Rithmic API to the latest version but there is a binary incompatibility resulting in unstable execution of the bridge program and this is the whole problem with these client-side API components which Rithmic is using. This is not something we can solve. It is for this reason, why it is that we cannot use the connection parameters that Rithmic is saying we should be using. In order for us to use those new connection parameters requires that we build the bridge program using those new parameters. However we cannot because there is this binary incompatibility between the current Visual C++ we use and libraries like open SSL and the Rithmic libraries resulting in unstable execution. We even tried to use the very latest Rithmic libraries. It does not help. However, there are very tiny differences between what they say we should be using and what we are using which matches the highlighted file in the attachment. We will be highlighting the differences later today. So why it is Rithmic cannot solve this issue from their side makes no technical sense to us. And we will be pointing that out to them soon as we go over the differences. ---- Our message to Rithmic today (2018-10-12): Hello Rithmic, As you may be aware users are having problem connecting to Rithmic from Sierra Chart today and we have been previously told the connection parameters we are using are out of date but we are using them from a file dated in June 2016. See the attachment: https://www.sierrachart.com/Download.php?Folder=SupportBoard&download=19796 We are using what is highlighted in red. We have tried using your very latest API files and the updated connection parameters, but we still have the problem with unstable execution when running the bridge program that we build with your libraries. The issue might have to do with Open SSL or some incompatibility that you are not aware of between the Visual C++ we are using which is 2017 and your version. We have to use our version of Open SSL because we rely Open SSL ourselves. When we say unstable execution what we actually notice is very early on in the execution of the bridge after Sierra Chart connects, there is a jump to a function that is not even getting called. The difference between the connection details we are using and what you are saying we should use, as you can see are very tiny. Can you please look at the differences. It does not make any sense you cannot resolve the issue from your side. There are no hardcoded IP addresses. Just domain names and other text names. 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: 2018-10-12 17:18:45
|
 Rithmic connection parameters folder.png / V - Attached On 2018-06-09 10:52:37 UTC - Size: 684.32 KB - 793 views |