Recent changes to bugs

Tag appear multiple times NOT a part of repeating group tag

Anne Tio — Tue, 08 Sep 2020 02:53:34 -0000

Hi,
We are currently using quickfixn, and we are having issue with the tag.
Tags appear multiple times randomly in some of the messages when there is a high load.. causing the message not being sent to the server. No other error log. We did not do any customization on the library.

Tag 9 appears twice
Tag 34, 49,52,56 appears 3x

20200907-06:00:37.994 : 8=FIX.4.4^9=246^9=310^35=D^34=60416^49=RakutenOOMS^52=20200907-06:00:37.993^56=RakutenBTS2^34=60417^49=RakutenOOMS^52=20200907-06:00:37.993^56=RakutenBTS2^1=066136706^11=0720629^22=99^38=300^40=2^44=9.00000000^48=7106^54=1^59=0^60=20200907-14:00:37.835^110=0^528=A^529=I^762=NM^453=2^448=00000^447=C^452=11^448=10065898^447=C^452=3^10=162^10=146^

20200907-06:00:37.994 : 8=FIX.4.4^9=246^9=310^35=G^34=60415^49=RakutenOOMS^52=20200907-06:00:37.973^56=RakutenBTS2^34=60418^49=RakutenOOMS^52=20200907-06:00:37.994^56=RakutenBTS2^1=063207104^11=0720630^38=2500^40=2^41=0664514^44=0.66000000^48=8907^54=2^59=0^60=20200907-14:00:37.851^110=0^529=I^762=NM^453=2^448=00000^447=C^452=11^448=10015482^447=C^452=3^10=153^10=139^
20200907-06:00:37.994 :

8=FIX.4.4^9=249^9=313^35=D^34=60414^49=RakutenOOMS^52=20200907-06:00:37.973^56=RakutenBTS2^34=60419^49=RakutenOOMS^52=20200907-06:00:37.994^56=RakutenBTS2^1=066962846^11=0720624^22=99^38=4000^40=2^44=0.19000000^48=71061D^54=1^59=0^60=20200907-14:00:37.754^110=0^528=A^529=I^762=NM^453=2^448=00000^447=C^452=11^448=10107491^447=C^452=3^10=065^10=055^

Logout message only coming through onLogout and not seeing reason. Not message in to/from Admin

Stan Bryl — Fri, 21 Jun 2019 00:57:23 -0000

Using python quckfix 1.15.1 and logging into ASX test enviroment. They are forcing a failover test and I need to get the seqNum of the logout message
Logon message goes out and is rejected with a logout; both message in my fix log.

I see the logon in the toAdmin and add my additional logon tags, and get the logout message back, but only the logout method is called, (nothing in fromAdmin or toAdmin methods) and I can't see the reason in the code as there is no message. I see the reason on the fix message. ASX is forcing a failover test and I need to get the last seq number and then add this to next logon as NextExpectedMsgSeqNum, but onLogout doesn't have the message so I can't parse tag 58 and see the reason nor get the seq number and use that in the NextExpectedMsgSeqNum tag value.

Messages are:
20190621-00:22:44.112711000 : 8=FIXT.1.19=10635=A34=149=TMAD252=20190621-00:22:44.11256=ASX98=0108=60141=Y553=TMAD2554=Aardvark201906!1137=910=181
20190621-00:22:44.338051000 : 8=FIXT.1.19=000012435=549=ASX56=TMAD234=952=20190621-00:22:44.2441409=10558=After fail-over, you MUST set next expected sequence number!10=083

How do I get get / trap this logout message so I can determine the NextExpectedMsgSeqNum and add to the next logon?

how to take backup of log file generated by QuickFix in .net

abhay — Mon, 13 May 2019 08:52:29 -0000

Hi Team ,
Can you please clarify on how to take the back up of log file generated by QuickFix in C# .Net and use of FileLogBackupPath in QuickFix config

I tried code snippet posted in this post, but not able to find the getSessions method in initiator object and getLog is also not present.

ArrayList sessions = initiator.getSessions();
{
foreach (var session in sessions)
{
SessionID sessionId = (SessionID)session;
Log logFile = Session.lookupSession(sessionId).getLog();
logFile.backup();
}
}

Compilation issue - Python - Building error

Guillaume Prevost — Mon, 21 May 2018 10:14:07 -0000

Hello
I am trying to build quickfix-1-15.1 for Python using comand "python setup.py install". Windows environment. I have Microsoft Visual Studio 14.0 installed.

First i got an issue with extra_compile_args, compilation failed because of the Wno-xxxx options. I removed them in setup.py and it fixed this issue.

Then it failed because of it could not find stdafx.h. I created an empty such file and it fixed this issue as well.

But now i am getting a new one that i cannot sort out. Compilation is working but it fails linking, see error message below. I am not sure how it cannot find the right libraries, can you help?

Thanks

Error message:

C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\BIN\link.exe /nologo /INCREMENTAL:NO /LTCG /DLL /MANIFEST:EMBED,ID=2 /MANIFESTUAC:NO /LIBPATH:C:\Python36\libs /LIBPATH:C:\Python36\PCbuild\win32 "/LIBPATH:C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\LIB" "/LIBPATH:C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\ATLMFC\LIB" "/LIBPATH:C:\Program Files (x86)\Windows Kits\10\lib\10.0.10240.0\ucrt\x86" "/LIBPATH:C:\Program Files (x86)\Windows Kits\8.1\lib\winv6.3\um\x86" /LIBPATH:\cib.net\ShareHK\Soft\Sybclient\oc_1251\OCS-12_5\lib /LIBPATH:\cib.net\ShareHK\Soft\Sybclient\oc_1251\ADO.NET\dll /EXPORT:PyInitquickfix build\temp.win32-3.6\Release\C++\HttpServer.obj build\temp.win32-3.6\Release\C++\TimeRange.obj build\temp.win32-3.6\Release\C++\ThreadedSSLSocketAcceptor.obj build\temp.win32-3.6\Release\C++\ThreadedSocketInitiator.obj build\temp.win32-3.6\Release\C++\QuickfixPython.obj build\temp.win32-3.6\Release\C++\MessageSorters.obj build\temp.win32-3.6\Release\C++\MySQLStore.obj build\temp.win32-3.6\Release\C++\Group.obj build\temp.win32-3.6\Release\C++\ThreadedSSLSocketConnection.obj build\temp.win32-3.6\Release\C++\SessionFactory.obj build\temp.win32-3.6\Release\C++\MessageStore.obj build\temp.win32-3.6\Release\C++\SSLSocketAcceptor.obj build\temp.win32-3.6\Release\C++\SocketInitiator.obj build\temp.win32-3.6\Release\C++\MySQLLog.obj build\temp.win32-3.6\Release\C++\Initiator.obj build\temp.win32-3.6\Release\C++\FieldTypes.obj build\temp.win32-3.6\Release\C++\FieldMap.obj build\temp.win32-3.6\Release\C++\OdbcLog.obj build\temp.win32-3.6\Release\C++\Utility.obj build\temp.win32-3.6\Release\C++\Settings.obj build\temp.win32-3.6\Release\C++\SocketAcceptor.obj build\temp.win32-3.6\Release\C++\SocketServer.obj build\temp.win32-3.6\Release\C++\pugixml.obj build\temp.win32-3.6\Release\C++\NullStore.obj build\temp.win32-3.6\Release\C++\PostgreSQLLog.obj build\temp.win32-3.6\Release\C++\OdbcStore.obj build\temp.win32-3.6\Release\C++\DataDictionary.obj build\temp.win32-3.6\Release\C++\ThreadedSocketAcceptor.obj build\temp.win32-3.6\Release\C++\FileStore.obj build\temp.win32-3.6\Release\C++\PostgreSQLStore.obj build\temp.win32-3.6\Release\C++\Log.obj build\temp.win32-3.6\Release\C++\FileLog.obj build\temp.win32-3.6\Release\C++\Acceptor.obj build\temp.win32-3.6\Release\C++\ThreadedSSLSocketInitiator.obj build\temp.win32-3.6\Release\C++\ThreadedSocketConnection.obj build\temp.win32-3.6\Release\C++\UtilitySSL.obj build\temp.win32-3.6\Release\C++\SessionSettings.obj build\temp.win32-3.6\Release\C++\HttpConnection.obj build\temp.win32-3.6\Release\C++\Session.obj build\temp.win32-3.6\Release\C++\PUGIXML_DOMDocument.obj build\temp.win32-3.6\Release\C++\HttpParser.obj build\temp.win32-3.6\Release\C++\SocketConnector.obj build\temp.win32-3.6\Release\C++\DataDictionaryProvider.obj build\temp.win32-3.6\Release\C++\SSLSocketConnection.obj build\temp.win32-3.6\Release\C++\SSLSocketInitiator.obj build\temp.win32-3.6\Release\C++\HttpMessage.obj build\temp.win32-3.6\Release\C++\FieldConvertors.obj build\temp.win32-3.6\Release\C++\Dictionary.obj build\temp.win32-3.6\Release\C++\SocketConnection.obj build\temp.win32-3.6\Release\C++\Message.obj build\temp.win32-3.6\Release\C++\Parser.obj build\temp.win32-3.6\Release\C++\SocketMonitor.obj /OUT:build\lib.win32-3.6_quickfix.cp36-win32.pyd /IMPLIB:build\temp.win32-3.6\Release\C++_quickfix.cp36-win32.lib
Creating library build\temp.win32-3.6\Release\C++_quickfix.cp36-win32.lib and object build\temp.win32-3.6\Release\C++_quickfix.cp36-win32.exp
QuickfixPython.obj : error LNK2001: unresolved external symbol impWSAGetLastError@0
Utility.obj : error LNK2001: unresolved external symbol impsetsockopt@20
Utility.obj : error LNK2001: unresolved external symbol impioctlsocket@12
Utility.obj : error LNK2001: unresolved external symbol imphtons@4
Utility.obj : error LNK2001: unresolved external symbol impgetsockopt@20
Utility.obj : error LNK2001: unresolved external symbol imprecv@16
Utility.obj : error LNK2001: unresolved external symbol impinet_ntoa@4
Utility.obj : error LNK2001: unresolved external symbol impconnect@12
Utility.obj : error LNK2001: unresolved external symbol impntohs@4
Utility.obj : error LNK2001: unresolved external symbol impsocket@12
Utility.obj : error LNK2001: unresolved external symbol impsend@16
Utility.obj : error LNK2001: unresolved external symbol impgetsockname@12
Utility.obj : error LNK2001: unresolved external symbol impinet_addr@4
Utility.obj : error LNK2001: unresolved external symbol impgetpeername@12
Utility.obj : error LNK2001: unresolved external symbol impWSAStartup@8
Utility.obj : error LNK2001: unresolved external symbol implisten@8
Utility.obj : error LNK2001: unresolved external symbol impshutdown@8
Utility.obj : error LNK2001: unresolved external symbol impgethostbyname@4
Utility.obj : error LNK2001: unresolved external symbol impclosesocket@4
Utility.obj : error LNK2001: unresolved external symbol impbind@12
Utility.obj : error LNK2001: unresolved external symbol impaccept@12
Utility.obj : error LNK2001: unresolved external symbol impWSACleanup@0
ThreadedSocketConnection.obj : error LNK2001: unresolved external symbol imp__select@20
build\lib.win32-3.6_quickfix.cp36-win32.pyd : fatal error LNK1120: 23 unresolved externals
error: command 'C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\BIN\link.exe' failed with exit status 1120

Documentation error

Paul_Tabo — Sat, 22 Nov 2014 01:49:45 -0000

On the web page:
http://www.quickfixengine.org/quickfix/doc/html/generating_databases.html

Under the heading "MSSQL" below, in the statement "You must have MySQL installed with ...." should have MySQL changed to MSSQL ?

Generating QuickFIX Databases

....

MSSQL

You must have MySQL installed with the deamon running.

Run the create script in src/sql/mssql. You must pass in a mssql user with permissions authorized to create a new database.

create.bat sa

....

Problem with connection timeout when connecting to an invalid ip

Sandeep — Fri, 06 Dec 2013 09:16:45 -0000

There seems to be an issue with connecting to an invalid ip, especially for ip's for which the dns resolution fails.

The connection attempt never gets timedout and so a new reconnection attempt is also not made.

We have observed this issue on both windows 64 and solaris amd64.

Additionally on Solaris amd64, it can also be observed while connecting to the loopback interface.

In both cases, we can see the library is trying to connect to the ip, but there will be no updates after that.

FIX.4.2-client-server::Connecting to ip_does_not_exist.com on port 19425

Solaris amd64
FIX.4.2-client-server::Connecting to 127.0.0.1 on port 13014

Problem with nextTargetMsgSeqNum incrementation

andrewm123 — Wed, 26 Jun 2013 13:40:59 -0000

The following problem was encountered. When a Logout message is received as the response on Logon message, the next target sequence number is incremented independently of the actual sequence number of the Logout message.

Example:
Let nextTargetMsgSeqNum = N
1) The sender sends Logon message
2) The target replies with Logout message having msgSeqNum = M, where M > N
3) The sender increments the nextTargetMsgSeqNum though msgSeqNum of received Logout message is higher than nextTargetMsgSeqNum

I expected that the nextTargetMsgSeqNum wouldn't be incremented in this situation.

I suggest to increment nextTargetMsgSeqNum conditionally when processing Logout message.

Example code:

private void nextLogout(Message logout) throws IOException, RejectLogon, FieldNotFound,
        IncorrectDataFormat, IncorrectTagValue, UnsupportedMessageType {
    if (!verify(logout, false, false)) {
        return;
    }

    String msg;
    if (!state.isLogoutSent()) {
        msg = "Received logout request";
        if (logout.isSetField(Text.FIELD)) {
            msg += ": " + logout.getString(Text.FIELD);
        }
        getLog().onEvent(msg);
        generateLogout(logout);
        getLog().onEvent("Sent logout response");
    } else {
        msg = "Received logout response";
        getLog().onEvent(msg);
    }

    state.setLogoutReceived(true);

    final int sequence = logout.getHeader().getInt(MsgSeqNum.FIELD);

    if (!isTargetTooHigh(sequence)) {
        state.incrNextTargetMsgSeqNum();
    }

    if (resetOnLogout) {
        resetState();
    }

    disconnect(msg, false);
}

In the current code nextTargetMsgSeqNum is incremented independently of the actual sequence number of the Logout message:

private void nextLogout(Message logout) throws IOException, RejectLogon, FieldNotFound,
        IncorrectDataFormat, IncorrectTagValue, UnsupportedMessageType {
    if (!verify(logout, false, false)) {
        return;
    }

    String msg;
    if (!state.isLogoutSent()) {
        msg = "Received logout request";
        if (logout.isSetField(Text.FIELD)) {
            msg += ": " + logout.getString(Text.FIELD);
        }
        getLog().onEvent(msg);
        generateLogout(logout);
        getLog().onEvent("Sent logout response");
    } else {
        msg = "Received logout response";
        getLog().onEvent(msg);
    }

    state.setLogoutReceived(true);

    state.incrNextTargetMsgSeqNum();

    if (resetOnLogout) {
        resetState();
    }

    disconnect(msg, false);
}

NextTargetMsgSeqNum wrongly incremented?

Gianni — Fri, 29 Mar 2013 16:53:16 -0000

When acting as initiator, if the sender sends a logon request and receives a logout the expected incoming sequence number is incremented independently of the actual sequence number of the logout message.
Example:
1) supposing NextTargetMsgSeqNum = N, the sender sends a logon request
2) the target replies with a logout message having sequence number N+M (where M>=0)
3) the sender disconnects BUT NextTargetMsgSeqNum is incremented

I was expected to have NextTargetMsgSeqNum not being changed.

acceptor issues logout after client logon after logout()

Stephen Oberski — Fri, 15 Mar 2013 18:52:45 -0000

This is a revisit of ID: 3047737

When the logout() method is used to force an acceptor to logout a connected client, subsequent attempts by the client to logon result in the acceptor immediately sending a logout after the initial logon messages are exchanged.

This is seen in version 1.13.3 of the quickfix engine.

The logout() method sets the enabled state in Session.cpp to false. On the next call to void Session::next( const UtcTimeStamp& timeStamp ) this forces the acceptor to send a logout to the client:

if( !isEnabled() || !isLogonTime(timeStamp) )
{
if( isLoggedOn() )
{
if( !m_state.sentLogout() )
{
m_state.onEvent( "Initiated logout request" );
generateLogout( m_state.logoutReason() );
}
}
else
return;
}

When the client attempts a subsequent logon, the enabled state is still false.

In void Session::nextLogon( const Message& logon, const UtcTimeStamp& timeStamp ) the enabled state is not changed so it remains false but the acceptor has sent a logon message to the client thus completing the logon sequence, the client now thinks it is logged on.

On the next call to void Session::next( const UtcTimeStamp& timeStamp ) the acceptor, seeing that the enabled state is still false generates a logout.

From this point on the client will continue to logon and be immediately logged out and there appears to be no way to change this behaviour.

If we look at how an explicit logout from the client is treated in void Session::nextLogout( const Message& logout, const UtcTimeStamp& timeStamp )
we see that the enabled state is not changed to false and the client is subsequently able to logon again without the spurious logout being sent by the acceptor.

I think it is reasonable to expect that the acceptor should be in the same state after a client initiated logout or a logout initiated by the logout() method.

As a work around, in Session.cpp, I have modified void Session::nextLogon( const Message& logon, const UtcTimeStamp& timeStamp ) to set the enabled state to true for an acceptor:

if ( !m_state.initiate()
|| (m_state.receivedReset() && !m_state.sentReset()) )
{
if( logon.isSetField(m_state.heartBtInt()) )
logon.getField( m_state.heartBtInt() );
m_state.onEvent( "Received logon request" );
generateLogon( logon );
m_state.onEvent( "Responding to logon request" );
this->logon(); // @@@
}
else
m_state.onEvent( "Received logon response" );

This appears to fix the immediate problem, and clients that are forced to logout by the acceptor can now successfully logon again.

Quickfix LogViewer: doesn't release closed file

Thomas — Thu, 24 Jan 2013 15:05:24 -0000

If you open a FIX-Log in the log viewer and you close it again, it is still blocked.