[This message was posted by Raj Dasgupta of UBS <[EMAIL PROTECTED]> to the 
"General Q/A" discussion forum at http://fixprotocol.org/discuss/22. You can 
reply to it on-line at http://fixprotocol.org/discuss/read/eb72c02b - PLEASE DO 
NOT REPLY BY MAIL.]

> > It appears that for clients using QuickFIX/J, if they try to connect
> > to a Cameron Engine with 141=Y in the Logon field, then Cameron
> > replies without the 141 tag. This causes the engines to go in a
> > strange state - QFG sends a second Logon as it does not recognize the
> > Acknowledgment, and then sends messages with SeqNum=1 again.
> 
> 141=Y was added to the specification so 24 hour sessions could be
> supported and sequence numbers re-established at 1 without the need to
> disconnect and reconnect. Using this flag when establishing a new
> session seems highly unusual. Most counterparties define a reset time.
> If you disconnect before the reset time and connect afterwards, you are
> using sequence number 1, and 141=Y is superfluous. If you are
> reconnecting intraday, in most cases 141=Y would be disastrous, as it
> would prevent recovery of missed messages while you were down.

Agreed. What I am getting to is that, there are *some* Initiators who inisist 
on re-establishing a new connection with SeqNum=1 and not the last known 
SeqNum. However on the Acceptor side, the SeqNum is still the last SeqNum at 
disconnection. Acceptor says "MesgSeqNum too low, expecting xxx but received 1" 
and disconnects the Initiator. The Initiator then tries to reconnect again, but 
this time with 141=Y to sync Seqs on both sides. This is when the problem 
occurs, and QFJ/Cameron communication runs into trouble and all these errors 
pop up.

Please note that this issue is mainly for counterparties who opt out of a 
"scheduled (bilateral) reset at a specific time of the day" and prefer sending 
a client-side request for resetting sequence numbers instead. Thanks in advance 
for your suggestions !


[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
-~----------~----~----~----~------~----~------~--~---

Reply via email to