Support Board
Date/Time: Wed, 27 Nov 2024 04:39:04 +0000
Post From: CTS disconnections
[2014-07-15 22:02:39] |
T44 - Posts: 363 |
Here is what our FIX team said:
Most of the sessions reported as "UnexpectedDisconnects" were actually normal FIX sessions. Take for instance, today's (7/14) T4CHART1 session reported in their July-disconnects log. Here is their log entry: VARacctnumber Yes ChartData SierraChart UnexpectedDisconnect 14 Jul 2014 11:12:38.883 AM 2 14 Jul 2014 11:11:39.000 AM 14 Jul 2014 11:12:38.883 AM VARipaddress:56013 VARhardwareID T4CHART1 4.2.0.0 FIX42 None False 0-0 0-0 0-0 0 0 3 2 2 0 0-0 0-0 0 0 0 0.0 0.0 1.0 In this chart data FIX session, our trace logs indicate that the user was logged on, heart-beated and successfully logged out per his request. Here are the corresponding FIX messages we received from the user: 1 - LOGIN (in 1) [14-Jul-2014] 11:11:39.6504284 [SenderCompID] 49 = SierraChart [TargetCompID] 56 = Dorman [MsgSeqNum] 34 = 1 [SendingTime] 52 = 20140714-16:11:39.597 [EncryptMethod] 98 = 0 (NONE) [HeartBtInt] 108 = 30 [ResetSeqNumFlag] 141 = Y (YES) [SecureDataLen] 90 = 36 [SecureData] 91 = //redacted [UserName] 553 = //redacted [Password] 554 = *** [DefaultApplExtID] 1407 = //redacted [NoMsgTypes] 384 = 1 [RefMsgType] 372 = V (ENABLE_CHART_DATA_SESSION) 2 - LOGIN (out 1) [MsgSeqNum] 34 = 1 [SenderCompID] 49 = Dorman [TargetCompID] 56 = SierraChart [SenderSubID] 50 = T4FIX [SendingTime] 52 = 20140714-16:11:39.712 [EncryptMethod] 98 = 0 (NONE) [HeartBtInt] 108 = 30 [UserName] 553 = //redacted [Password] 554 = *** [DefaultCstmApplVerID] 1408 = 4.3.8.0 3 - HEARTBEAT (in 2) [SenderCompID] 49 = SierraChart [TargetCompID] 56 = Dorman [MsgSeqNum] 34 = 2 [SendingTime] 52 = 20140714-16:12:09.641 4 - HEARTBEAT (out 2) [MsgSeqNum] 34 = 2 [SenderCompID] 49 = Dorman [TargetCompID] 56 = SierraChart [SenderSubID] 50 = T4FIX [SendingTime] 52 = 20140714-16:12:09.696 5 - LOGOUT (in 3) [SenderCompID] 49 = SierraChart [TargetCompID] 56 = Dorman [MsgSeqNum] 34 = 3 [SendingTime] 52 = 20140714-16:12:38.313 6 - LOGOUT (out 3) [14-Jul-2014] 11:12:38.3689316 [MsgSeqNum] 34 = 3 [SenderCompID] 49 = Dorman [TargetCompID] 56 = SierraChart [SenderSubID] 50 = T4FIX [SendingTime] 52 = 20140714-16:12:38.368 [Text] 58 = Successful logout upon request There are also other sessions disconnected per a dropped socket - most likely, a networking issue. So my question for Sierra Chart support would be why is Sierra Chart requesting to drop the FIX connection with CTS when I have active symbols in the intraday update list and when I am running several charts of live markets? The second issue appears to be a network issue - dropped sockets which I understand Sierra Support (and possibly even CTS) may not be able to help with. I am going to try the FIX logging instructions tomorrow although without heartbeat information I'm not sure how helpful this will be to CTS support. Thanks. |