Thread: [Quickfix-users] SendingTime accuracy problem causes client disconnect.
Brought to you by:
orenmnero
Menu
▾
▴
quickfix-users
|
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 |
|
From: Ted G. <tg...@Co...> - 2008-05-15 20:22:05
|
It appears from your mail that you are taking more than 2 minutes to process a message. Am I understanding you correctly that incoming messages are staying in the inbound queue for 120 seconds? If so, I think you should investigate why it is taking so long to process messages, rather than raise your SendingTime threshold. Ted -----Original Message----- From: qui...@li... [mailto:qui...@li...] On Behalf Of Rodrick Brown Sent: Thursday, May 15, 2008 12:34 PM To: qui...@li...; qui...@li... Subject: [Quickfix-users] SendingTime accuracy problem causes clientdisconnect. QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html QuickFIX Support: http://www.quickfixengine.org/services.html 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 ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Quickfix-users mailing list Qui...@li... https://lists.sourceforge.net/lists/listinfo/quickfix-users |
|
From: Rodrick B. <rod...@gm...> - 2008-05-15 21:46:25
|
This was a stress test thanks to all for the fix works like a charm. On Thu, May 15, 2008 at 4:21 PM, Ted Graham <tg...@co...> wrote: > > It appears from your mail that you are taking more than 2 minutes to process > a message. > > Am I understanding you correctly that incoming messages are staying in the > inbound queue for 120 seconds? If so, I think you should investigate why it > is taking so long to process messages, rather than raise your SendingTime > threshold. > > Ted > > -----Original Message----- > From: qui...@li... > [mailto:qui...@li...] On Behalf Of Rodrick > Brown > Sent: Thursday, May 15, 2008 12:34 PM > To: qui...@li...; > qui...@li... > Subject: [Quickfix-users] SendingTime accuracy problem causes > clientdisconnect. > > QuickFIX Documentation: > http://www.quickfixengine.org/quickfix/doc/html/index.html > QuickFIX Support: http://www.quickfixengine.org/services.html > > 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 > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Quickfix-users mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfix-users > > > -- [ Rodrick R. Brown ] http://www.rodrickbrown.com http://www.linkedin.com/in/rodrickbrown |
|
From: Djalma R. d. S. F. <drs...@gm...> - 2008-05-15 20:23:15
|
Yes, this is quickfix behavior, but you can set CheckLatency=N or increase the MaxLatency value. On Thu, May 15, 2008 at 3:33 PM, Rodrick Brown <rod...@gm...> wrote: > QuickFIX Documentation: > http://www.quickfixengine.org/quickfix/doc/html/index.html > QuickFIX Support: http://www.quickfixengine.org/services.html > > 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 > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Quickfix-users mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfix-users > |
|
From: Rodrick B. <rod...@gm...> - 2008-05-15 22:38:27
|
It seems with this option in place we're no longer seeing the reject message. Is there anyway to still have this reject message generated and not drop the client? On Thu, May 15, 2008 at 4:22 PM, Djalma Rosa dos Santos Filho <drs...@gm...> wrote: > Yes, this is quickfix behavior, but you can set CheckLatency=N or increase > the MaxLatency value. > > On Thu, May 15, 2008 at 3:33 PM, Rodrick Brown <rod...@gm...> > wrote: >> >> QuickFIX Documentation: >> http://www.quickfixengine.org/quickfix/doc/html/index.html >> QuickFIX Support: http://www.quickfixengine.org/services.html >> >> 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 >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2008. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> _______________________________________________ >> Quickfix-users mailing list >> Qui...@li... >> https://lists.sourceforge.net/lists/listinfo/quickfix-users > > -- [ Rodrick R. Brown ] http://www.rodrickbrown.com http://www.linkedin.com/in/rodrickbrown |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X