{{Quickfixn}} SeqNum sync

Wed Jan 9 10:46:50 PST 2019

Mike,

No I am using QuickFIxN in a very plain vanilla way - not doing anything special.

I use multiple threads, but I can't see how the innard of QuickFIXN could be used by more than one, by anything I have coded. IS there a way Mike?

Unfortunately, I have wiped the part after that in the log, but it went on to function normally there after.

Lawrence

________________________________
From: Quickfixn <quickfixn-bounces at lists.quickfixn.com> on behalf of Dominique Normand <dominique.normand at gmail.com>
Sent: 09 January 2019 14:07
To: 'Mailing list for QuickFIX/n'
Subject: Re: {{Quickfixn}} SeqNum sync

Are you sending messages from concurrent threads?

From: Quickfixn [mailto:quickfixn-bounces at lists.quickfixn.com] On Behalf Of Mike Gatny
Sent: January-09-19 8:47 AM
To: Mailing list for QuickFIX/n <quickfixn at lists.quickfixn.com>
Subject: Re: {{Quickfixn}} SeqNum sync

This should never happen because the only place where the sender seqnum is incremented is in Session.SendRaw, which is protected by a mutex.

So:: are you doing something unusual like calling IncrNextSenderMsgSeqNum manually?  Or manually setting the MsgSeqNum field on your messages?

Also:

- Which version of quickfix/n are you using? The latest is v1.8.0.

- Can you post some more of that message log, i.e. after the heartbeat where 34=1364?

--

Mike Gatny

Connamara Systems

On Wed, Jan 9, 2019 at 6:29 AM Gabe Barwick <barwickhome at hotmail.com<mailto:barwickhome at hotmail.com>> wrote:

Hi,

I am regularly (1 or 2 times per day) sending FIX messages with SeqNum out of sequence.

20190107-11:43:31.174 : 8=FIX.4.4 9=70 35=0 34=1361 49=SenderID 52=20190107-11:43:31.143 56=TargetID 10=192

20190107-11:44:01.122 : 8=FIX.4.4 9=0070 35=0 49=TargetID 56=SenderID 34=1415 52=20190107-11:44:01.123 10=028

20190107-11:44:01.186 : 8=FIX.4.4 9=70 35=0 34=1362 49=SenderID 52=20190107-11:44:01.153 56=TargetID 10=192

20190107-11:44:31.141 : 8=FIX.4.4 9=0070 35=0 49=TargetID 56=SenderID 34=1416 52=20190107-11:44:31.141 10=032

20190107-11:44:31.187 : 8=FIX.4.4 9=70 35=0 34=1363 49=SenderID 52=20190107-11:44:31.165 56=TargetID 10=199

20190107-11:45:01.160 : 8=FIX.4.4 9=0070 35=0 49=TargetID 56=SenderID 34=1417 52=20190107-11:45:01.160 10=032

20190107-11:45:01.404 : 8=FIX.4.4 9=209 35=D 34=1365 49=SenderID 52=20190107-11:45:01.393 56=TargetID <Hidden> 10=102

20190107-11:45:01.408 : 8=FIX.4.4 9=70 35=0 34=1364 49=SenderID 52=20190107-11:45:01.198 56=TargetID 10=204

What might be causing QuickFixN to do this?

How can I minimise the number of times this happens?

Lawrence

_______________________________________________
Quickfixn mailing list
Quickfixn at lists.quickfixn.com<mailto:Quickfixn at lists.quickfixn.com>
http://lists.quickfixn.com/listinfo.cgi/quickfixn-quickfixn.com<https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.quickfixn.com%2Flistinfo.cgi%2Fquickfixn-quickfixn.com&data=02%7C01%7C%7C4ac8dec13849413d240008d6763bdddc%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636826396836632241&sdata=qasVKrHJJ9cVdarSZAhkZ6dH8DCBmrLN8i6XuOJgwOg%3D&reserved=0>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.quickfixn.com/pipermail/quickfixn-quickfixn.com/attachments/20190109/289a384f/attachment.htm>