[This message was posted by Hanno Klein of Deutsche Börse Systems <[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/89852640 - PLEASE DO NOT REPLY BY MAIL.]
Seems a little harsh to disconnect the session as soon as a single message is received with an invalid tag. Application level messages such as OrderStatusRequest or NewOrderSingle will not do you any harm. The rejection allows the submitter to take action and "try again", obviously after he has changed something. A rogue application firing invalid messages at you is a different story. Have a look at the FIX Session protocol where severe scenarios are described when you should terminate the session. An invalid tag is a simple error. > Dear All, > > As a SELL side, we are issuing session level reject message (35 = 3) if > tag not defined for message type is sent by the BUY side. (We are FIX > 4.2. compliant) > > After session level rejection we are disconnecting the session also. > > Can we follow session disconnection after session level rejection > or allow all other incoming mesage request without disconnecting > the session? > > Thanks in advance. [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.
