Support Board
Date/Time: Mon, 03 Feb 2025 08:03:05 +0000
Post From: Trade Activity Log spamming "connecting to SC order routing" every millisecond
[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 |