Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Fri, 26 Apr 2024 22:28:43 +0000
Report: Sunday June 18, 2017 Data and Web server Interruptions
View Count: 2511
| [2017-06-20 02:12:56] |
| |
|
1. On Sunday, June 18, 2017, 5 of the real-time server processes running on our servers, had run into an access violation exception and shutdown. This affected the following real-time services: FXCM Forex/CFD data Crypto currency data Market Statistics ( the stock exchanges these are based on were closed, so no effect.) LMAX Real-time data Normally these processes are extremely reliable and do not encounter such a problem. We continue to enhance our real-time and historical server programs to be very reliable and efficient. We worked very hard today to determine what the problem is and we discovered what it was and resolved it. It was a minor issue that required only two lines of code to resolve. In most cases, the issue would not cause an access violation exception. The real-time server program is of very high technical quality and very high-performance. And while it did encounter a problem, we understood what the issue was and the particular oversight. It is permanently resolved. For LMAX, we also set up a second redundant server today. Our Historical server program is also going to be converted to a 64-bit process to handle the increased load. For the time being, we are going to set up a parallel Historical data server process. 2. Also on Sunday, the Sierra Chart Web server was nonresponsive at times and slow to serve a response to a web request. This is actually what indirectly triggered the real-time server problem above, but was not the underlying reason. This issue was resolved Sunday evening. It was only a configuration issue preventing the Web server process from handling a high number of requests at a time. Some users said that the Sierra Chart Web server was down Saturday/Sunday, and someone said for a few hours on Sunday. The actual problems that existed are described in items 1 or 2 here. Originally when we were asked about the Sierra Chart website being down, we had thought it was due to an IP address change since we were not observing the website being down ourselves. The IP address change seemed to be the only logical conclusion at the time we were asked, but we did know the other server at the old IP was running. But we thought somehow it was associated with that. It is now clear, the problem was primarily what was described in item 1 above. 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-06-20 04:42:24
|
To post a message in this thread, you need to log in with your Sierra Chart account: