Posted: Feb 20, 2014 @ 06:26 PM             Msg. 1 of 7

After establishing a FAST session, we do not receive any heartbeat messages within the 30 seconds specified time.

---

Thank You,
Sierra Chart Engineering

Posted: Feb 20, 2014 @ 06:29 PM             Msg. 2 of 7

Please specify username, environment and time of the case

---

Victor Vins
Lead Software Developer

Posted: Feb 20, 2014 @ 07:27 PM             Msg. 3 of 7

Username: SierraChartTM

Environment : API

Log (Time zone is US Eastern):

OEC FAST Market Data session: Disconnecting due to a loss of activity. No activity for at least 48 seconds. | 2014-02-20 19:26:22

OEC FAST Market Data session: Sending a Logout message. Text = Disconnecting due to loss of activity. | 2014-02-20 19:26:22

OEC FAST Market Data session: Remote side disconnected without completing the logout sequence. Final messages may have been lost, although unlikely. | 2014-02-20 19:26:22

Connection to the external service has been lost. | 2014-02-20 19:26:22

---

Thank You,
Sierra Chart Engineering

Posted: Feb 21, 2014 @ 11:47 AM             Msg. 4 of 7

It is possible that we skip some pings. Please consider using higher timeout.

---

Victor Vins
Lead Software Developer

Posted: Mar 12, 2014 @ 07:14 PM             Msg. 5 of 7

A higher timeout will not help because your FAST protocol is not delivering any heartbeats at all.

I have verified this by setting a breakpoint in the function that receives data from the socket. It was never it. In the test, I did not subscribe to any symbols and there were no heartbeats.

This needs to get resolved.

This is critical problem.

---

Thank You,
Sierra Chart Engineering

Posted: Mar 12, 2014 @ 10:07 PM             Msg. 6 of 7

Our test client application tells us that heartbeats come as expected. You can direct your application to API environment - our server has detailed logs enabled there.

---

Victor Vins
Lead Software Developer

Posted: Mar 12, 2014 @ 10:26 PM             Msg. 7 of 7

I can see they are coming now:

2014-03-13 15:23:44 | OEC FAST Data (Recv) >> [ID: 62] 35=0
52=20140313022335
<80, 044A-1441-501E-FF>
2014-03-13 15:23:49 | OEC FAST Data (Recv) >> [ID: 62] 35=0
52=20140313022340
<80, 044A-1441-501F-84>
2014-03-13 15:23:53 | OEC FAST Data (Send) << [ID: 62] 35=0
52=20140313022353
<80, 044A-1441-501F-91>
2014-03-13 15:23:54 | OEC FAST Data (Recv) >> [ID: 62] 35=0
52=20140313022345
<80, 044A-1441-501F-89>
2014-03-13 15:23:59 | OEC FAST Data (Recv) >> [ID: 62] 35=0
52=20140313022350
<80, 044A-1441-501F-8E>

I did not test this recently. I had tested this when I originally posted in the thread and they were not coming at that time. And also there was a report from a user about two weeks ago also indicating the heartbeats were not coming.

I can see this is now resolved. I had another report today of a problem that I thought may have been due to heartbeats but I can see it is not.

Thank you.

---

Thank You,
Sierra Chart Engineering