[This message was posted by John Prewett of Lava Trading <[email protected]> to the "Certification" discussion forum at http://fixprotocol.org/discuss/9. You can reply to it on-line at http://fixprotocol.org/discuss/read/67309249 - PLEASE DO NOT REPLY BY MAIL.]
There are two questions in your posting: 1. How should we respond? 2. Should this be happening at all? I'm going to answer this in reverse order. 2. Should this be happening at all? No. Something is going wrong with your FIX engine or its interface to your application, or both. If you have already received and processed a message with a certain MsgSeqNum and the FIX engine gives it to you again (same MsgSeqNum), something is going very badly wrong. The application should only be processing incoming messages with an ever-increasing MsgSeqNum. The situation you describe should not be happening. 1. How do we respond? Due to the fact that the situation should not be happening, I would terminate the FIX session, alert your support staff and delegate the problems away from your automated system to humans. Good luck. Sounds nasty. JohnP [You can unsubscribe from this discussion group by sending a message to mailto:[email protected]] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Financial Information eXchange" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/fix-protocol?hl=en -~----------~----~----~----~------~----~------~--~---
