Thread: [Quickfix-developers] Suppressing the QuickFix automatic logout response
Brought to you by:
orenmnero
Menu
▾
▴
quickfix-developers
|
From: mvictoryAtgmail <mvi...@gm...> - 2007-11-07 20:52:24
|
When my client sends a message with a sequence number lower than the server is expecting, I get a logout message from the server with the error: MsgSeqNum too high, expecting 136 but received 1 I catch this message in my fromAdmin function within my application, and parse it to figure out what number I need to reset my sequence number to. (I can't find anywhere but my fromAdmin function that can see this message.) Unfortunately, QuickFix insists on sending a logout response to the logout message I received. My server does not expect a logout response, and it causes some sync issues before I can get reconnected. My question is: How can I suppress that logout response from QuickFix? I receive a message of type 5 from the server, but in the case of this particular error, I want to handle it myself. In my toAdmin function, I can see the logout message that I'm trying to suppress, but I can't figure out a way to get rid of it. I tried using Dispose() but that causes a crash. I also tried changing it to a heartbeat but it didn't stop quickFix from sending the logout message. Thanks! -- View this message in context: http://www.nabble.com/Suppressing-the-QuickFix-automatic-logout-response-tf4767298.html#a13635834 Sent from the QuickFIX - Dev mailing list archive at Nabble.com. |
|
From: Djalma R. d. S. F. <drs...@gm...> - 2007-11-07 21:11:08
|
I suspect that in toAdmin() you can also throw FIX::DoNotSend. On Nov 7, 2007 6:52 PM, mvictoryAtgmail <mvi...@gm...> wrote: > QuickFIX Documentation: > http://www.quickfixengine.org/quickfix/doc/html/index.html > QuickFIX Support: http://www.quickfixengine.org/services.html > > > When my client sends a message with a sequence number lower than the > server > is expecting, I get a logout message from the server with the error: > > MsgSeqNum too high, expecting 136 but received 1 > > I catch this message in my fromAdmin function within my application, and > parse it to figure out what number I need to reset my sequence number to. > (I > can't find anywhere but my fromAdmin function that can see this message.) > > Unfortunately, QuickFix insists on sending a logout response to the logout > message I received. My server does not expect a logout response, and it > causes some sync issues before I can get reconnected. > > My question is: > How can I suppress that logout response from QuickFix? I receive a > message > of type 5 from the server, but in the case of this particular error, I > want > to handle it myself. > > In my toAdmin function, I can see the logout message that I'm trying to > suppress, but I can't figure out a way to get rid of it. I tried using > Dispose() but that causes a crash. I also tried changing it to a > heartbeat > but it didn't stop quickFix from sending the logout message. > > Thanks! > -- > View this message in context: > http://www.nabble.com/Suppressing-the-QuickFix-automatic-logout-response-tf4767298.html#a13635834 > Sent from the QuickFIX - Dev mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Quickfix-developers mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfix-developers > |
|
From: mvictoryAtgmail <mvi...@gm...> - 2007-11-07 23:05:53
|
I can't throw FIX::DoNotSend within toAdmin. Throwing DoNotSend works in toApp, but the problematic logout message does not go through toApp. As best I can tell, the only place I can intercept that logout message is in toAdmin, but I can't seem to do anything useful to it. Djalma Rosa dos Santos Filho wrote: > > QuickFIX Documentation: > http://www.quickfixengine.org/quickfix/doc/html/index.html > QuickFIX Support: http://www.quickfixengine.org/services.html > > > I suspect that in toAdmin() you can also throw FIX::DoNotSend. > > On Nov 7, 2007 6:52 PM, mvictoryAtgmail <mvi...@gm...> wrote: > >> QuickFIX Documentation: >> http://www.quickfixengine.org/quickfix/doc/html/index.html >> QuickFIX Support: http://www.quickfixengine.org/services.html >> >> >> When my client sends a message with a sequence number lower than the >> server >> is expecting, I get a logout message from the server with the error: >> >> MsgSeqNum too high, expecting 136 but received 1 >> >> I catch this message in my fromAdmin function within my application, and >> parse it to figure out what number I need to reset my sequence number to. >> (I >> can't find anywhere but my fromAdmin function that can see this message.) >> >> Unfortunately, QuickFix insists on sending a logout response to the >> logout >> message I received. My server does not expect a logout response, and it >> causes some sync issues before I can get reconnected. >> >> My question is: >> How can I suppress that logout response from QuickFix? I receive a >> message >> of type 5 from the server, but in the case of this particular error, I >> want >> to handle it myself. >> >> In my toAdmin function, I can see the logout message that I'm trying to >> suppress, but I can't figure out a way to get rid of it. I tried using >> Dispose() but that causes a crash. I also tried changing it to a >> heartbeat >> but it didn't stop quickFix from sending the logout message. >> >> Thanks! >> -- >> View this message in context: >> http://www.nabble.com/Suppressing-the-QuickFix-automatic-logout-response-tf4767298.html#a13635834 >> Sent from the QuickFIX - Dev mailing list archive at Nabble.com. >> >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Splunk Inc. >> Still grepping through log files to find problems? Stop. >> Now Search log events and configuration files using AJAX and a browser. >> Download your FREE copy of Splunk now >> http://get.splunk.com/ >> _______________________________________________ >> Quickfix-developers mailing list >> Qui...@li... >> https://lists.sourceforge.net/lists/listinfo/quickfix-developers >> > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Quickfix-developers mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfix-developers > -- View this message in context: http://www.nabble.com/Suppressing-the-QuickFix-automatic-logout-response-tf4767298.html#a13638113 Sent from the QuickFIX - Dev mailing list archive at Nabble.com. |
|
From: Heiko T. <hti...@gt...> - 2007-11-08 07:13:01
|
I'd like to know what others did. I allow the Logout message to be sent. I then stop QuickFix, set the sender and target sequence numbers to what the server expects and then log back in. The sequence numbers can be set by calling setNextSenderMsgSeqNum() and setNextTargetMsgSeqNum() on the FileStore. Resetting of sequence numbers is only done if a Logout is received in response to a Login i.e. the FIX session has not yet been setup. This prevents any loss of application FIX messages. mvictoryAtgmail wrote: > QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html > QuickFIX Support: http://www.quickfixengine.org/services.html > > > I can't throw FIX::DoNotSend within toAdmin. > Throwing DoNotSend works in toApp, but the problematic logout message does > not go through toApp. As best I can tell, the only place I can intercept > that logout message is in toAdmin, but I can't seem to do anything useful to > it. > > > > Djalma Rosa dos Santos Filho wrote: > >> QuickFIX Documentation: >> http://www.quickfixengine.org/quickfix/doc/html/index.html >> QuickFIX Support: http://www.quickfixengine.org/services.html >> >> >> I suspect that in toAdmin() you can also throw FIX::DoNotSend. >> >> On Nov 7, 2007 6:52 PM, mvictoryAtgmail <mvi...@gm...> wrote: >> >> >>> QuickFIX Documentation: >>> http://www.quickfixengine.org/quickfix/doc/html/index.html >>> QuickFIX Support: http://www.quickfixengine.org/services.html >>> >>> >>> When my client sends a message with a sequence number lower than the >>> server >>> is expecting, I get a logout message from the server with the error: >>> >>> MsgSeqNum too high, expecting 136 but received 1 >>> >>> I catch this message in my fromAdmin function within my application, and >>> parse it to figure out what number I need to reset my sequence number to. >>> (I >>> can't find anywhere but my fromAdmin function that can see this message.) >>> >>> Unfortunately, QuickFix insists on sending a logout response to the >>> logout >>> message I received. My server does not expect a logout response, and it >>> causes some sync issues before I can get reconnected. >>> >>> My question is: >>> How can I suppress that logout response from QuickFix? I receive a >>> message >>> of type 5 from the server, but in the case of this particular error, I >>> want >>> to handle it myself. >>> >>> In my toAdmin function, I can see the logout message that I'm trying to >>> suppress, but I can't figure out a way to get rid of it. I tried using >>> Dispose() but that causes a crash. I also tried changing it to a >>> heartbeat >>> but it didn't stop quickFix from sending the logout message. >>> >>> Thanks! >>> -- >>> View this message in context: >>> http://www.nabble.com/Suppressing-the-QuickFix-automatic-logout-response-tf4767298.html#a13635834 >>> Sent from the QuickFIX - Dev mailing list archive at Nabble.com. >>> >>> >>> ------------------------------------------------------------------------- >>> This SF.net email is sponsored by: Splunk Inc. >>> Still grepping through log files to find problems? Stop. >>> Now Search log events and configuration files using AJAX and a browser. >>> Download your FREE copy of Splunk now >> http://get.splunk.com/ >>> _______________________________________________ >>> Quickfix-developers mailing list >>> Qui...@li... >>> https://lists.sourceforge.net/lists/listinfo/quickfix-developers >>> >>> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Splunk Inc. >> Still grepping through log files to find problems? Stop. >> Now Search log events and configuration files using AJAX and a browser. >> Download your FREE copy of Splunk now >> http://get.splunk.com/ >> _______________________________________________ >> Quickfix-developers mailing list >> Qui...@li... >> https://lists.sourceforge.net/lists/listinfo/quickfix-developers >> >> > > -- Heiko Tillwick Mail: hti...@gt... Tel: +27 11 214 8062 Fax: +27 11 214 8028 Web: www.gt247.co.za Global Trader 1st Floor, 10 Melrose Boulevard, Melrose Arch, 2196 This message is confidential. If you are not the intended recipient, the reading, use, transmission or disclosure of its contents is prohibited. |
