Imported from previous forum
when a client logged with heart beat different than we had set up in the configuration file
example client had 120secs we had only 30secs… my question is will log on message will allowed ???
yes, you should login without problem, the server and the client sends heartbeat message independently and the counterpart shall reply it to keep the conenction up.
server will send heartbeat every 30 seconds, and the client should reply it or else server send a TEST message.
same thin on client side, it must send a heartbeat message every 120 seconds to check if the server connection is up.
Cheers,
Clebson Derivan
when a client logged with heart beat different than we had set up in the
configuration file example client had 120secs we had only 30secs… my
question is will log on message will allowed ???
[Start Quote from FIX.4.0 spec page 8/67 of doc]
The heartbeat interval is declared by the session initiator using the HeartBtInt field in the Logon message.
[End Quote]
This is better clarified in FIX.4.3
[Start Quote from FIX.4.3 spec page 3/63 of vol 2 pdf]
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”.
[End Quote]
So the Session Acceptor should accept whatever HeartBeatInt (108) is provided by Session Initiator in the initiating Logon message.
The Session initiator might even choose to disconnect the Session if the HeartBeatInt in the reply Logon message is not equal to the value initially sent out by the Session Initiator in the initiating Logon message.
yes, you should login without problem, the server and the client sends
heartbeat message independently and the counterpart shall reply it to
keep the conenction up.server will send heartbeat every 30 seconds, and the client should reply
it or else server send a TEST message.same thin on client side, it must send a heartbeat message every 120
seconds to check if the server connection is up.Cheers, Clebson Derivan
when a client logged with heart beat different than we had set up in
the configuration file example client had 120secs we had only 30secs…
my question is will log on message will allowed ???
you are right, thank you for the clarification.
[Start Quote from FIX.4.0 spec page 8/67 of doc]
The heartbeat interval is declared by the session initiator using the
HeartBtInt field in the Logon message.[End Quote]
This is better clarified in FIX.4.3
[Start Quote from FIX.4.3 spec page 3/63 of vol 2 pdf]
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”.[End Quote]
So the Session Acceptor should accept whatever HeartBeatInt (108) is
provided by Session Initiator in the initiating Logon message.The Session initiator might even choose to disconnect the Session if
the HeartBeatInt in the reply Logon message is not equal to the
value initially sent out by the Session Initiator in the initiating
Logon message.yes, you should login without problem, the server and the client sends
heartbeat message independently and the counterpart shall reply it to
keep the conenction up.server will send heartbeat every 30 seconds, and the client should
reply it or else server send a TEST message.same thin on client side, it must send a heartbeat message every 120
seconds to check if the server connection is up.Cheers, Clebson Derivan
when a client logged with heart beat different than we had set up in
the configuration file example client had 120secs we had only
30secs… my question is will log on message will allowed ???