Re: [Quickfix-developers] Sending 141=Y
Brought to you by:
orenmnero
|
From: Oren M. <or...@qu...> - 2006-04-29 17:19:12
|
MessageThere is not a configuration setting for this right now (we need = one). Currently, this has to be accomplished by adding a little bit of = code. In order to accomplish this, you need to have your application = reset() the session in onCreate(). This would ensure that the session = would always have reset sequence numbers after a crash. --oren ----- Original Message -----=20 From: Ajay Kamdar=20 To: qui...@li...=20 Sent: Friday, April 28, 2006 7:29 AM Subject: [Quickfix-developers] Sending 141=3DY It seems to me that there is a problem in consistently sending 141=3DY = in a Logon even when ResetOnLogout, ResetOnDisconnect, and = SendResetSeqNumFlag are all set to Y for a session.=20 When using FIX4.1 and higher, QuickFix decides to set 141=3DY when = initiating a Logon if 1. one of the session config attributes ResetOnLogout, = ResetOnDisconnect, or SendResetSeqNumFlag is set to Y 2. and if the expected sender and target sequence numbers are equal to = 1 When ResetOnLogout and ResetOnDisconnect are set, QuickFix will reset = the sequence numbers to 1 upon a graceful session logout or abrupt = disconnect, the above conditions will be satisfied, and the next Logon = message will contain 141=3DY. However, if the engine process were to = crash for whatever reason, the sequence numbers will NOT be equal to 1 = because QuickFix never got the opportunity to reset the sequence = numbers. Hence when the initiator sends a Logon after the process is = restarted, its Logon will not contain 141=3DY even though all the = necessary configuration attributes are set correctly. From a logical perspective, IMHO in this case it should not make any = difference whether a connection to a counter party was broken because of = a Logout, socket disconnect, or engine crash. Any ideas how to make = QuickFix consistently send 141=3DY with the out of the box configuration = attributes without having to add additional logic in the application? Thanks, - Ajay = ________________________________________________________________________ The information in this email is confidential and may be legally = privileged. It is intended solely for the addressee. Access to this email by = anyone else is unauthorized. If you are not the intended recipient, any = disclosure, copying, distribution or any action taken or omitted to be taken in reliance on = it, is prohibited and may be unlawful. TradeWeb reserves the right to monitor and review the content of all = messages sent to or from this e-mail address. Messages sent to or from this e-mail = address may be stored on the TradeWeb e-mail system. |