Re: [Quickfixj-users] Issue related to message recovery

[Christoph J. <chr...@fo...>]

Hi


Queued messages are not processed until the resend request has been satisfied. E.g. if you are waiting for a resend of messages up to seqnum 1000, all seqnums lower than 1000 are not processed until message seqnum 1000 has been received.

Cheers
Chris


--

Christoph John

Software Engineering



[X]

Foconis Trading GmbH

Oppenhoffallee 103

52066 Aachen



Web: https://foconis.com<https://foconis.com/>

E-Mail: chr...@fo...<mailto:chr...@fo...>

Tel.: +49 241 557080 28 / Zentrale-0



Geschäftsführer: Peter Kretzmann, George Macdonald

Amtsgericht Hamburg: HRB 46346 | USt-IDNr.: DE118680003
Unsere Hinweise zum Datenschutz sind hier zu entnehmen (Artikel 13, 14 und 21 EU-DSGVO):

https://group.foconis.com/datenschutz



________________________________
From: Ankit Mehta <ank...@gm...>
Sent: 31 January 2026 09:25
To: qui...@li... <qui...@li...>
Subject: [Quickfixj-users] Issue related to message recovery

You don't often get email from ank...@gm.... Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
hi team,

We had an issue recently wherein there was a disconnection on the acceptor side.
The initiator rightly failed over to the second host and sent a resend request, which was fulfilled by the server as well.
The instability persisted and we noticed multiple resend requests were sent in between.
What we noticed though, during the time the application was catering to processing re-sent messages, when new messages were coming in at the same time they were getting queued up.

We saw lines like below in the events logs:

MsgSeqNum too high expecting <> but received <> ....
Enqueued at pos: <num>

In ideal scenarios, which I can see for certain messages in the beginning, we see log like this:
Processing queued message: <num>

But we do not see this happening for the majority of these new trade messages causing the messages to be eventually missed.

We are on quickfix all version 2.3.0.
Would anyone have seen such an issue and can opine what could have happened?

Regards,
Ankit