|
4.0 Session
< Previous Next >
Re: Session Level rejections
Eva Schmidt
8 Jan 2008 4:26AM ETHi Senthil,
thanks for your reply.
> I am not sure whether you are referring to session level or message
> level mandatory fields, in any case if a session level message could be
> generated for the invalid incoming message, it means message could be
> decrypted,bodylength and checksum are passed.
In my case a good example would be an ExecutionReport Message without the mandatory Symbol tag (55). This will be rejected by my engine with a Session Level Reject Message.
>
> In this case, Rejected messages should be logged and the incoming
> sequence number incremented. Otherwise it may end up with infinite
> resend loop.
>
So, ok - in this case it would be better to increment the SeqNum. Are there any cases in which incrementing could lead to a desaster situation? Should I difference Session Level mandatory fields (like TargetCompID, Checksum etc.) from Application Level mandatory fields?
Thanks a lot,
Eva
Re: Session Level rejections
Eva Schmidt 8 Jan 2008 4:26AM ET
|
