{{Quickfixn}} Log In troubles [I]

[Erika Hernandez]

Classification: For internal use only

Hi ,

Unfortunately I'm getting stuck again. 

According to the log , I think my problem is related to the sequence 
number that is expected is different to the seq number I'm trying to sent 
. am I right?

regarding to a previous e- mail , I got these doubts :


1)   I debugged the code, when I try to send the order , I see that the 
Send methods are executed twice. Why? 

When this line is executed for second time :


   int bytesSent = socket_.Send(rawData);


I get the  last event on the log:

20131125-22:29:40.220 : Created session
20131125-22:29:40.274 : Connecting to 172.17.111.23 on port 9002
20131125-22:29:40.286 : Connection succeeded
20131125-22:30:14.975 : Connection failed: An existing connection was 
forcibly closed by the remote host

And the order is not sent. 


2 , 3  ) Yes , I already tried : 

ResetOnLogon=Y
MsgSeqNum=1


But it did't work , and ,  that's right, I cannot restart the sequence 
number from the other side every time i need to run my code since there 
will be used on automated test cases , I think I  need to know the next 
sequence number before sending  the message. 

So I think the right settings will be: 

ResetOnLogon=N


How can I get the last seq number used? 

Where  the sequence number is being set ? 

Why a zero is sent  here? : 

 public virtual bool Send(Message message)
        {
            message.Header.RemoveField(Fields.Tags.PossDupFlag);
            message.Header.RemoveField(Fields.Tags.OrigSendingTime);
            return SendRaw(message, 0); 
        }

I guess the sequence number is taken from here, so should I add that to 
the message's header? 

 protected void Persist(Message message, string messageString)
        {
            if (this.PersistMessages)
            {
                int msgSeqNum = message.Header.GetInt(Fields.Tags
.MsgSeqNum);
                state_.Set(msgSeqNum, messageString);
            }
            state_.IncrNextSenderMsgSeqNum();
        }



Any  suggestion or guidelines would be really appreciated! 

Thanks & regards! 




********************************************************************************************************
This email is sent to you by Infosys Limited on behalf of Deutsche Bank.
Diese email wurde Ihnen von Infosys Limited im Auftrag der Deutschen Bank 
gesendet
********************************************************************************************************* 




From:
Ashutosh Mishra <A.Mishra at ny.tr.mufg.jp>
To:
Mailing list for QuickFIX/n <quickfixn at lists.quickfixn.com>, 
Date:
11/26/2013 09:35 AM
Subject:
Re: {{Quickfixn}} Log In troubles [I]



Hi Grant,
                Thanks for the reply. Got lot of things resolved by your 
reply.
 
Thanks & Regards,
Ashutosh Mishra
 
*********************************************************************************
This communication (including any attachments) is intended only or the use 
of the individual whom it is addressed and may contain information that is 
privileged, confidential or legally protected.  If the reader of this 
message is not the intended recipient, you are hereby notified that any 
dissemination, distribution or copying of this communication is strictly 
prohibited. If you have received this communication in error, please 
notify us immediately by replying to the message.  Please also delete the 
message and its attachments, if any, from your computer and destroy any 
hard copies you may have created.  Thank you for your cooperation. 
*********************************************************************************
 
From: quickfixn-bounces at lists.quickfixn.com [
mailto:quickfixn-bounces at lists.quickfixn.com] On Behalf Of Grant 
Birchmeier
Sent: Monday, November 25, 2013 5:13 PM
To: Mailing list for QuickFIX/n
Subject: Re: {{Quickfixn}} Log In troubles [I]
 
1) 
The message 
"
An Existing connection was forcibly closed by the remote host
" means that the other side is terminating the connection.  You may not 
know why.
 
2) 
"
MsgSeqNum
=1" -- Ashutosh, I don't know what this means.  That's not a setting.  If 
you put it in your config, QF will ignore it.
 
3) Asking the other side to reset their sequence numbers is not a great 
idea.  They'll probably refuse.
 
Your ResetOnXXX settings must match up with their interface.  If they 
don't reset on logon, you shouldn't either.  You can manually edit your 
.seqnums file between app executions to match their expectation, or you 
can let the transport layer fix itself with resend requests or whatnot. (I 
forget the exact msg flow at the moment; in some scenarios the two sides 
will work it out, in others they won't.)
 
 
 _______________________________________________
Quickfixn mailing list
Quickfixn at lists.quickfixn.com
http://lists.quickfixn.com/listinfo.cgi/quickfixn-quickfixn.com




---
This communication may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this communication
in error) please notify the sender immediately and destroy this
communication. Any unauthorized copying, disclosure or distribution of the
material in this communication is strictly forbidden.

Deutsche Bank does not render legal or tax advice, and the information
contained in this communication should not be regarded as such.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.quickfixn.com/pipermail/quickfixn-quickfixn.com/attachments/20131126/9aa4e447/attachment-0002.htm>