[This message was posted by Taras Orel of EPAM Systems <[email protected]> to the "4.0 Session" discussion forum at http://fixprotocol.org/discuss/12. You can reply to it on-line at http://fixprotocol.org/discuss/read/97379ae7 - PLEASE DO NOT REPLY BY MAIL.]
Looks like your system act like acceptor in case when it receives Logon response. Do you have only one session (initiator) configured on your side? > Hello Everyone, > I am using quickfixj to connect to connect to a Exchange/Broker which also > uses quickfix. > > The FIX session settings on my end are as follows: > [DEFAULT] > StartTime=00:00:00 > EndTime=00:00:00 > ConnectionType=initiator > SLF4JLogHeartbeats=N > UseDataDictionary=Y > HeartBtInt=30 > CheckLatency=N > [SESSION] > FileStorePath=qf_store/sim_store > FileLogPath=qf_store/sim_log > TargetCompID=XXXXXX > SocketConnectPort=9652 > SenderCompID=XXXXXX > DataDictionary=XXXXXXXX > SocketConnectHost=XXXXXXXX > BeginString=FIX.4.2 > > The FIX session settings on the Exchange/Broker end are as follows: > [DEFAULT] > BeginString=FIX.4.2 > SenderCompID=XXXXX > ConnectionType=acceptor > SocketAcceptPort=9652 > SocketReuseAddress=N > StartTime=00:00:00 > EndTime=00:00:00 > ResetOnLogon=N > LogoutTimeout=100 > NicIpAddress=XXXXXXXXX > CheckLatency=N > SocketNodelay=Y > PersistMessages=Y > FileStorePath=..\\logs\\FIX_STORE > FileLogPath=..\\logs\\FIX_LOGS > DataDictionary=..\\config\\FO_FIX42.xml > > #BeginSession_XXXXX > [SESSION] > TargetCompID=24512,11893,1 > #EndSession_XXXXX > > Events as seen by my system: > 20100924-14:01:53: Created session: > 20100924-14:01:54: Initiated logon request > 20100924-14:01:54: Received logon request (Problem) > 20100924-14:01:55: Responding to logon request > 20100924-14:01:55: quickfix.SessionException MsgSeqNum too low, expecting 2 > but received 1 > 20100924-14:01:55: Disconnecting > > Message log: > > 8=FIX.4.2 9=110 35=A 34=1 49=XXX 52=20100924-14:01:54.540 56=XXX 95=6 > 96=092100 98=0 108=30 141=Y 554=XXX 10=081 > 8=FIX.4.2 9=188 35=A 34=1 49=XXX 52=20100924-14:02:08.343 56=XXX 98=0 > 108=30 554=XXX 925= 6002=A 6003=XXX 6004=XXX > 6006=A 6014=2 10=015 > 8=FIX.4.2 9=110 35=A 34=1 49=XXX 52=20100924-14:01:54.728 56=XXX 95=6 > 96=092100 98=0 108=30 141=Y 554=XXX 10=089 > 8=FIX.4.2 9=113 35=3 34=1 49=XXX 52=20100924-14:02:08.734 56=XXX 45=1 > 58=This is duplicate login message. 372=A 10=037 > 8=FIX.4.2 9=143 35=g 34=2 49=XXX 52=20100924-14:01:55.103 56=XXX 263=1 > 335=1285336913462 6015=2 6001=20100924-14:01:55 6001=20100924-14:01:55 > 10=111 > 8=FIX.4.2 9=79 35=h 34=2 49=XXX 52=20100924-14:02:08.890 56=XXX 336=18 > 340=2 10=010 > 8=FIX.4.2 9=115 35=5 34=3 49=XXX 52=20100924-14:01:55.119 56=XXX > 58=MsgSeqNum too low, expecting 2 but received 1 10=071 > > The issue as I see it, is that my system treats the incoming logon response > as a request (even though it is an initiator) and sends a response back. > Which causes the system to fail with msq seq. num errors. > > Anyone has any idea on why this could be happening and how I could solve it. > > Thanks > Zain [You can unsubscribe from this discussion group by sending a message to mailto:[email protected]] -- You received this message because you are subscribed to the Google Groups "Financial Information eXchange" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/fix-protocol?hl=en.
