[Quickfix-users] Session resync problem

[Sean K. <sea...@pi...>]

Hello All,

We had an issue in our production environment that boiled down to the =
following:

1. Client has hard disconnect
2. We send some messages prior to detecting the session is down
3. Client logs back in with higher than expected seq num and immediately =
starts sending some messages
4. We send resend reqs for each message we receive until they are =
handled, which the client does by
    sending us seq reset messages.
5. The client heartbeats.
6. At this point, we do some message resending.
-- this is where the trouble began --
7. Since the client did not sync its seq nums after the logon, when we =
start sending these messages they
    have higher than expected seq nums.
8. Client sends a resend request for each of the messages we sent (125).

When processing the resend requests, the engine sits in a tight loop =
processing its queue.  The trouble
here is that the resend requests took approx. 5 minutes to get through =
and all other connections were
starved.

Has anyone come across this problem, or have a suggestion for dealing =
with it gracefully?

Regards,

Sean Kirkpatrick