[Quickfix-users] SendingTime accuracy problem causes client disconnect.
Brought to you by:
orenmnero
From: Rodrick B. <rod...@gm...> - 2008-05-15 18:34:10
|
We're processing orders from queue which can get fairly large some orders end up being processed after the default SendingTime (120s). We then send back "Message 569 Rejected: SendingTime accuracy problem" back to the client which causes our client to disconnect is this the correct behavior? We dont want our client to be disconnected on these types of rejects. Has anyone else seen this? 20080515-17:55:58: Acceptor heartbeat set to 45 seconds 20080515-17:55:58: Logon contains ResetSeqNumFlag=Y, resetting sequence numbers to 1 20080515-17:55:58: Received logon request 20080515-17:55:58: Responding to logon request 20080515-18:00:20: Message 569 Rejected: SendingTime accuracy problem 20080515-18:00:20: Message 570 Rejected: SendingTime accuracy problem 20080515-18:00:20: Disconnecting -- [ Rodrick R. Brown ] http://www.linkedin.com/in/rodrickbrown |