Heartbeat set as 108=0 ...?

, ,
1

Imported from previous forum

2

Hello,

I can see some of my customers logged in using a zero heartbeat interval, which seems to generate on average 3 heartbeats from their systems to ours per second, which is quite overkill imho.

Does the protocol define anything for this? Should 108=0 be possible in your opinion?

Regards,
Chris

3

[ original email was from Khody Azmoon - khody.azmoon@gmail.com ]
Chris,

I am not sure if there is a recommended optimum time, but QuickFIX defaults it to 30 seconds, and some of the brokerages I have come across specify 30 seconds in their documentation.

Also per FIX 4.2 documentation: The HeartBtInt value should be agreed upon by the two firms and specified by the Logon initiator and echoed back by the Logon acceptor. Note that the same HeartBtInt value is used by both sides, the Logon “initiator” and Logon “acceptor”.

Regards,

Khody

Hello,

I can see some of my customers logged in using a zero heartbeat interval, which seems to generate on average 3 heartbeats from their systems to ours per second, which is quite overkill imho.

Does the protocol define anything for this? Should 108=0 be possible in your opinion?

Regards,
Chris

4

Hello,

I can see some of my customers logged in using a zero heartbeat interval, which seems to generate on average 3 heartbeats from their systems to ours per second, which is quite overkill imho.

Does the protocol define anything for this? Should 108=0 be possible in your opinion?

Regards,
Chris

In some systems HBI=0 means that there should be no heartbeats in this session between counterparties.

5

[ original email was from John Prewett - jprewett@lavatrading.com ]
According to the FIX.4.2 specification:
“If HeartBtInt is set to zero then no regular heartbeat messages will be generated”

Thanks

JohnP

Hello,

I can see some of my customers logged in using a zero heartbeat interval, which seems to generate on average 3 heartbeats from their systems to ours per second, which is quite overkill imho.

Does the protocol define anything for this? Should 108=0 be possible in your opinion?

Regards,
Chris

6

[ original email was from Abhay Srivastava - abhay.srivastava@credit-suisse.com ]
As per Doc,

. If HeartBtInt is set to zero then no regular heartbeat messages will be generated. Note that a test request message can still be sent independent of the value of the HeartBtInt, which will force a Heartbeat message.

-Abhay

As the heartbeat concept is integral to session integrity I would suggest that you define a valid heartbeat interval range with your customer i.e. say you accept between 30 seconds and 90 seconds or something.

Hello,

I can see some of my customers logged in using a zero heartbeat interval, which seems to generate on average 3 heartbeats from their systems to ours per second, which is quite overkill imho.

Does the protocol define anything for this? Should 108=0 be possible in your opinion?

Regards,
Chris