Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Sun, 05 May 2024 03:48:40 +0000
Trade Activity Log spamming "connecting to SC order routing" every millisecond
View Count: 699
| [2019-10-31 13:04:56] |
| T44 - Posts: 363 |
|
"Connecting to SC order routing server: futurestrading6.sierracharts.com:11098" appears in the trade activity log 1-2x per millisecond. I assume this is going to use a lot of resources on operations which process the log. Is there a way for me to remove these entries/clear the log while keeping my fill data? |
 10014-2019-10-31-1302.png / V - Attached On 2019-10-31 13:04:26 UTC - Size: 297.67 KB - 225 views |
| [2019-10-31 14:01:20] |
| |
|
Ok, that is completely unexpected. That is the address of the London server but there should not be any repetitive messages like that. Can we call you now? This is considered a serious issue.
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-10-31 15:13:48] |
| T44 - Posts: 363 |
|
I'm sorry it's not a good time to take a call immediately. Can you message me a number to reach you on and I'll try sometime later today...meanwhile you can have a copy of my installation directory (or any subset of files in it) if that would be useful?
|
| [2019-10-31 19:14:41] |
| User379468 - Posts: 508 |
|
What SC version is this problem happening on? Was about to switch to this setup and want to avoid.
|
| [2019-10-31 19:42:10] |
| |
|
We are going to take care of this issue for the user. We have no idea why it is happening in their particular case, and it makes no sense, and no other user is experiencing it, and we do not see any problem. It makes no technical sense. It is puzzling to even see something like this. Once we understand it, we will take the appropriate steps for the user or or do code changes to ensure it does not happen. But really this whole thing is very strange to begin with. It is technically impossible for there to be connections at that rate. There has never been any case of anything like this in the history of the program. So we don't understand what is going on here. You should have absolute no concern about this. It is not going to affect you. 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-10-31 19:45:14] |
| T44 - Posts: 363 |
|
Thank you Engineering, I look forward to some feedback on this issue. I've noticed quite a bit of lag on the platform coincident with this issue and I'd rather not trade while a "serious issue" is outstanding. I'm a little concerned that such issues are making it into production, release early release often has benefits but I'd like my trading front end to be stable. Can you let me know what the next steps are to help resolve please. Would a call still be helpful or is there other information I could share? |
| [2019-10-31 20:24:04] |
| |
|
Are you available now for us to look into this? And we really as we indicated above have absolutely no idea about this problem and it is very very puzzling to us. It is not something we or other users see. And we cannot even see why it would technically happen. You should not have been using Sierra Chart at all with a problem like this. This is why we offered to call immediately.
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-10-31 20:28:41] |
| T44 - Posts: 363 |
|
Certainly, I am available. Can you let me know which number is best to call you on? I shall check private account tickets. And I can confirm the issue is still occurring with version 2006. Date Time Of Last Edit: 2019-10-31 20:33:40
|
| 10025-2019-10-31-2033.png / V - Attached On 2019-10-31 20:33:21 UTC - Size: 298.14 KB - 225 views |
| [2019-10-31 20:35:12] |
| |
|
We can give you a number to call by private ticket but it would be easiest if we just call your number. Can we do that? We are referring to the number you have here: https://www.sierrachart.com/UserControlPanel.php?page=ManageAccountInfo 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-10-31 20:35:35
|
| [2019-10-31 20:39:34] |
| |
|
Do you use Skype? We sent you a ticket now with a Skype username. Let us know if that works. Otherwise we will give you another number.
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-10-31 21:16:34] |
| |
|
We are releasing now prerelease version 2007 which we expect will resolve this issue. For diagnostic purposes so we can isolate the triggering event, we have added a diagnostic log message to the Message Log in this version.
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-10-31 21:32:16] |
| T44 - Posts: 363 |
|
Thank you, I shall update now and report back.
|
| [2019-10-31 21:38:01] |
| T44 - Posts: 363 |
|
Thank you this is indeed resolved for me in Prerelease 2007.
|
| [2019-11-01 07:10:05] |
| T44 - Posts: 363 |
|
For diagnostic purposes so we can isolate the triggering event, we have added a diagnostic log message to the Message Log in this version. I do have this in my message logs... + GetAppropriateHDClient called | 2019-11-01 02:09:02.760
+ GetAppropriateHDClient called | 2019-11-01 02:09:02.760 + GetAppropriateHDClient called | 2019-11-01 02:09:02.761 + GetAppropriateHDClient called | 2019-11-01 02:09:02.761 + GetAppropriateHDClient called | 2019-11-01 02:09:02.762 + GetAppropriateHDClient called | 2019-11-01 02:09:02.762 + GetAppropriateHDClient called | 2019-11-01 02:09:02.763 + GetAppropriateHDClient called | 2019-11-01 02:09:02.763 + GetAppropriateHDClient called | 2019-11-01 02:09:02.764 + GetAppropriateHDClient called | 2019-11-01 02:09:02.764 + GetAppropriateHDClient called | 2019-11-01 02:09:02.765 + GetAppropriateHDClient called | 2019-11-01 02:09:02.765 + GetAppropriateHDClient called | 2019-11-01 02:09:02.766 + GetAppropriateHDClient called | 2019-11-01 02:09:02.766 + GetAppropriateHDClient called | 2019-11-01 02:09:02.767 + GetAppropriateHDClient called | 2019-11-01 02:09:02.767 + GetAppropriateHDClient called | 2019-11-01 02:09:02.768 + GetAppropriateHDClient called | 2019-11-01 02:09:02.768 + GetAppropriateHDClient called | 2019-11-01 02:09:02.769 + GetAppropriateHDClient called | 2019-11-01 02:09:02.769 + GetAppropriateHDClient called | 2019-11-01 02:09:02.770 + GetAppropriateHDClient called | 2019-11-01 02:09:02.770 + GetAppropriateHDClient called | 2019-11-01 02:09:02.771 + GetAppropriateHDClient called | 2019-11-01 02:09:02.771 + GetAppropriateHDClient called | 2019-11-01 02:09:02.772 + GetAppropriateHDClient called | 2019-11-01 02:09:02.772 + GetAppropriateHDClient called | 2019-11-01 02:09:02.773 + GetAppropriateHDClient called | 2019-11-01 02:09:02.773 + GetAppropriateHDClient called | 2019-11-01 02:09:02.774 + GetAppropriateHDClient called | 2019-11-01 02:09:02.774 + GetAppropriateHDClient called | 2019-11-01 02:09:02.775 + GetAppropriateHDClient called | 2019-11-01 02:09:02.775 + GetAppropriateHDClient called | 2019-11-01 02:09:02.776 + GetAppropriateHDClient called | 2019-11-01 02:09:02.776 + GetAppropriateHDClient called | 2019-11-01 02:09:02.778 + GetAppropriateHDClient called | 2019-11-01 02:09:02.779 + GetAppropriateHDClient called | 2019-11-01 02:09:02.780 + GetAppropriateHDClient called | 2019-11-01 02:09:02.782 + GetAppropriateHDClient called | 2019-11-01 02:09:02.783 + GetAppropriateHDClient called | 2019-11-01 02:09:02.784 + GetAppropriateHDClient called | 2019-11-01 02:09:02.785 + GetAppropriateHDClient called | 2019-11-01 02:09:02.786 + GetAppropriateHDClient called | 2019-11-01 02:09:02.788 + GetAppropriateHDClient called | 2019-11-01 02:09:02.789 + GetAppropriateHDClient called | 2019-11-01 02:09:02.790 + GetAppropriateHDClient called | 2019-11-01 02:09:02.792 + GetAppropriateHDClient called | 2019-11-01 02:09:02.793 + GetAppropriateHDClient called | 2019-11-01 02:09:02.794 + GetAppropriateHDClient called | 2019-11-01 02:09:02.795 + GetAppropriateHDClient called | 2019-11-01 02:09:02.796 |
| [2019-11-01 09:36:23] |
| |
|
Do you notice this continuously? You should not. If you do, that indicates a problem we need to look into. If charts are continuously reloading for some other reason, you would see those messages. In this case, refer to: High CPU Usage | Inactive User Interface | Poor Performance | Long Time to Load Chart Data | Charts Reloading Often: 30.3 - Charts Reloading Often 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-11-01 09:37:41
|
| [2019-11-02 09:37:55] |
| T44 - Posts: 363 |
|
No, its not continuous, and I don't view the message log unless there is a problem so not affecting what I'm doing, thanks.
|
| [2019-11-02 10:35:11] |
| |
|
That is good. Therefore, we consider that there is no remaining issue 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-11-02 10:35:19
|
To post a message in this thread, you need to log in with your Sierra Chart account: