[Quickfix-developers] Session issue
Brought to you by:
orenmnero
|
From: Nick V. <ni...@ad...> - 2006-03-29 09:51:13
|
I'm using QF 1.11.0 for Java and FIX 4.2 and am experiencing some odd behaviour while doing some session level tests. I have an initiator (QuickFIX) and an acceptor (not QuickFix) that I have started and allowed to exchange heartbeats for a few minutes. I then stop both of them and set the expected message sequence number of the acceptor back by 5. I then restart both the initiator and the acceptor and would expect to see the initiator log onto the acceptor and then send a sequence reset message, followed by a normal exchange of heartbeats going forward. However, what actually happens is that after logging, sending the sequence reset message, and then sending the first heartbeat (to which the acceptor correctly responds), the initiator then sends a logout message and the session is terminated. This isn't really what I'd expect. Any thoughts?? Thanks Nik ************************************************************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized use of the information contained in this email or its attachments is prohibited. If this email is received in error, please contact the sender and delete the material from your computer systems. Do not use, copy, or disclose the contents of this email or any attachments. Abu Dhabi Investment Authority (ADIA) accepts no responsibility for the content of this email to the extent that the same consists of statements and opinions made which are the senders own and not made on behalf of ADIA. Nor does ADIA accept any liability for any errors or omissions in the content of this email caused by electronic and technical failures. Although ADIA has taken reasonable precautions to ensure that no viruses are present in this email, ADIA accepts no responsibility for any loss or damage arising from the use of this email or its attachments. ************************************************************************************************************** |