[Quickfix-developers] FIX Session Dropped
Brought to you by:
orenmnero
|
From: Nick V. <ni...@ad...> - 2006-12-04 16:01:26
|
I'm using QF 1.11.0 for Java. I've implemented a class that extends quickfix.MessageCracker and implements quickfix.Application. In my implementation, each FIX application message I receive needs to update certain records in the DB behind my investment management system. I've noticed that on rare occasions, this can take up to a minute and prevents my application from sending heartbeat messages. This results in my counterparty sending a test request, which I'm unable to process, since my application is still busy trying to update my database, which then causes the counterparty to drop the FIX session. Does anyone have any suggestions how to manage this? I thought of spawning a new thread for each FIX application message I receive, which would process the message, but is there a better way? 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. ************************************************************************************************************** |