{{Quickfixn}} System.Net.Sockets.SocketException (10054)

Mario Alberti cid.mizar at gmail.com
Tue May 11 09:02:26 PDT 2021


I changed the library from QuickFix.Net.NETCore.FIX50SP2
to QuickFIXn.FIX5.0SP2 and started working normally apparently. Even the
problem with MessageCracker that was never call, started been recognized

My project is a netcoreapp3.1




El lun, 10 may 2021 a las 22:47, Mario Alberti (<cid.mizar at gmail.com>)
escribió:

> Are there any other reasons to have "58=*Incorrect BeginString" *besides
> having a different dictionary than your counterpart?
>
> I'm using the dictionary that the counterpart says it must be used.
>
> Thanks you in advance
>
> El mar, 4 may 2021 a las 17:32, Mario Alberti (<cid.mizar at gmail.com>)
> escribió:
>
>> What could be the reason of this exception?
>> 20210504-20:12:41.452 : Created session
>> 20210504-20:12:41.475 : Connecting to 127.0.0.1 on port 8080
>> 20210504-20:12:41.513 : Connection succeeded
>> 20210504-20:12:41.521 : Session reset: ResetOnLogon
>> 20210504-20:12:41.537 : Session reset: ResetSeqNumFlag
>> 20210504-20:12:41.540 : Initiated logon request
>> 20210504-20:12:42.424 : Sequence numbers reset due to ResetSeqNumFlag=Y
>> 20210504-20:12:42.426 : Received logon
>>
>>
>>
>> *20210504-20:12:43.435 : Session FIXT.1.1:USER->NQT disconnecting:
>> System.Net.Sockets.SocketException (10054): An existing connection was
>> forcibly closed by the remote host   at
>> QuickFix.SocketInitiatorThread.ReadSome(Byte[] buffer, Int32
>> timeoutMilliseconds)   at
>> QuickFix.SocketInitiatorThread.Read()20210504-20:12:43.437 : Session reset:
>> ResetOnDisconnect*
>>
>>
>> *----CaseLogon is successfully done, after that I ask for the
>> securityList and I got the first securityListResponse and then the logout
>> is forced. The same happens with *NewOrderSingle, it is place in the
>> market with no trouble but push me to logout.
>>
>> 20210504-20:12:41.539 : 8=FIXT.1.1 9=126 35=A 34=1 49=USER
>> 52=20210504-20:12:41.523 56=NQT 98=0 108=30 141=Y 553=USER 554=password
>> 1137=9 10=223
>> 20210504-20:12:42.401 : 8=FIXT.1.1 9=90 35=A 34=1 49=NQT
>> 52=20210504-20:12:43.108 56=USER 98=0 108=30 141=Y 1137=9 10=146
>> 20210504-20:12:42.430 : 8=FIXT.1.1 9=117 *35=x* 34=2 49=USER
>> 52=20210504-20:12:42.430 56=NQT 115=USER 128=NQT 263=1 320=012 559=4 10=131
>> 20210504-20:12:42.871 : 8=FIXT.1.1 9=28049 35=y 34=2 49=NQT
>> 52=20210504-20:12:43.366 56=USER 320=012 322=597242963205519 393=293 559=4
>> 560=0 893=Y LONGMESSAGEXXXX 10=233
>> 20210504-20:12:42.886 : 8=FIXT.1.1 9=90 35=5 34=3 49=USER
>> 52=20210504-20:12:42.886 56=NQT 58=*Incorrect BeginString* 10=219
>> 20210504-20:12:42.887 : 8=FIXT.1.1 9=477 35=y 34=3 49=NQT
>> 52=20210504-20:12:43.369 56=USER 320=012 322=597242964876827 393=293 559=4
>> 560=0 893=Y LONGMESSAGEXXXX 10=028
>> 20210504-20:12:42.896 : 8=FIXT.1.1 9=90 35=5 34=4 49=USER
>> 52=20210504-20:12:42.895 56=NQT 58=*Incorrect BeginString* 10=220
>> 20210504-20:12:42.896 : 8=FIXT.1.1 9=444 35=y 34=4 49=NQT
>> 52=20210504-20:12:43.369 56=USER 320=012 322=597242964907371 393=293 559=4
>> 560=0 893=Y LONGMESSAGEXXXX 10=160
>>
>> The counterparty says that they received and respond with no exception
>> the message. So they are no forcing the logout, according to them.
>>
>> Any idea would be helpfull.
>>
> _______________________________________________
> Quickfixn mailing list
> Quickfixn at lists.quickfixn.com
> http://lists.quickfixn.com/listinfo.cgi/quickfixn-quickfixn.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.quickfixn.com/pipermail/quickfixn-quickfixn.com/attachments/20210511/9051352e/attachment.htm>


More information about the Quickfixn mailing list