简体   繁体   English

Fix.4.2协议实现(Fiximulator-Banzai(client))消息日志

[英]Fix.4.2 protocol implementation(Fiximulator - Banzai(client)) message log

I am trying to implement Fix.4.2 protocol, but It is difficult to understand the message log I attached below. 我正在尝试实现Fix.4.2协议,但是很难理解我在下面附加的消息日志。 Here Logon(35=A) request was sent with MsgSeqNum(34=1) from client. 在这里,Logon(35 = A)请求是与客户端发送的MsgSeqNum(34 = 1)一起发送的。 Then for testing ResendRequest and SequenceReset session level messages I sent a NewOrderSingle request with MsgSeqNum=7 (instead of MsgSeqNum=2, as subsequent messages should have incremeted msgseqnum after logon request). 然后,为了测试ResendRequest和SequenceReset会话级别消息,我发送了一个MsgSeqNum = 7的NewOrderSingle请求(而不是MsgSeqNum = 2,因为在登录请求后,后续消息应该具有msgseqnum)。 As expected MsgSeqNum is too high than recieved one Fiximulator responded with a ResendRequest(35=2) to send from 2 to 0 (ie, from 2 to 7). 正如预期的那样,MsgSeqNum太高而无法接收,一个Fiximulator响应了ResendRequest(35 = 2),无法从2发送到0(即从2发送到7)。 Here why the Fiximulator is not waiting for client's reply ? 在这里,为什么Fiximulator不等待客户的答复? instead it is sending an heartbeat message. 相反,它发送的是心跳消息。 Why the client is sending ResendRequest in response to ResendRequest of Fiximulator instead of sending SequenceReset message ?. 为什么客户端发送ResendRequest来响应Fiximulator的ResendRequest而不是发送SequenceReset消息?

Also explain remaining cases if possible. 如果可能,还请说明其余情况。

Thanks in advance. 提前致谢。 在此处输入图片说明

What is your status of ResetOnLogon in your config file for the acceptor ? 您的接受器配置文件中的ResetOnLogon状态如何? Default value is N so it isn't being reset. 默认值为N,因此不会重置。 Always check your config file or try debugging to figure out issues. 始终检查您的配置文件或尝试调试以找出问题。

ResetOnLogon Determines if sequence numbers should be reset when recieving a logon request. ResetOnLogon确定在接收登录请求时是否应重置序列号。 Acceptors only 仅接受者

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM