Urgent need to handle resend request !

, ,
1

Imported from previous forum

2

LP server send me resend request to send messages( check tag 7 & Tag 16 )

8=FIX.4.49=8135=249=blabla56=blabla34=138852=20100105-05:43:34.1477=8716=010=083

I sent sequence reset-reset mode(not gapfill) higher than expected seq num (plz chaeck tag 36)

8=FIX.4.49=5235=449=blabla56=blabla34=8743=Y52=1/5/2010 11:13:42123=N36=9110=33

but they again gives resend request

8=FIX.4.49=8135=249=blabla56=blabla34=138952=20100105-05:43:41.8817=8716=010=087

How to handle this situation?
Thanks in advance.

3

[ original email was from Bivas Mishra - bivas.mishra@wipro.com ]
Hi,
I noticed the following in your Seq-Reset message header:
“52=1/5/2010 11:13:42”
timestamp not in UTC format.

Apart from this, are you trying to recover a session by sending a sequence reset?

As per FIX4.4 Specs, vol-2, Pg-23, the sequence reset (Reset Mode message should not be used in the scenario you depicted unless it is a disaster recovery scenario.

To Quote the specs…
“Sequence Reset – Reset should NOT be used as a normal response to a Resend Request (use Sequence Reset – Gap Fill mode). The Sequence Reset – Reset should ONLY be used to recover from a disaster situation which cannot be recovered via the use of Sequence Reset – Gap Fill. Note that the use of Sequence Reset – Reset may result in the possibility of lost messages.”

Regards,
Bivas

LP server send me resend request to send messages( check tag 7 & Tag 16
)

8=FIX.4.49=8135=249=blabla56=blabla34=138852=20100105-
05:43:34.1477=8716=010=083

I sent sequence reset-reset mode(not gapfill) higher than expected seq
num (plz chaeck tag 36)

8=FIX.4.49=5235=449=blabla56=blabla34=8743=Y52=1/5/2010
11:13:42123=N36=9110=33

but they again gives resend request

8=FIX.4.49=8135=249=blabla56=blabla34=138952=20100105-
05:43:41.8817=8716=010=087

How to handle this situation? Thanks in advance.

4

I think, that Sequence Reset-Reset message was identified as garbled (tag 52 is not in UTC format) and ignored so counterparty sent Resend Request again.

Hi, I noticed the following in your Seq-Reset message header:
“52=1/5/2010 11:13:42” timestamp not in UTC format.

Apart from this, are you trying to recover a session by sending a
sequence reset?

As per FIX4.4 Specs, vol-2, Pg-23, the sequence reset (Reset Mode
message should not be used in the scenario you depicted unless it is a
disaster recovery scenario.

To Quote the specs… “Sequence Reset – Reset should NOT be used as a
normal response to a Resend Request (use Sequence Reset – Gap Fill
mode). The Sequence Reset – Reset should ONLY be used to recover from a
disaster situation which cannot be recovered via the use of Sequence
Reset – Gap Fill. Note that the use of Sequence Reset – Reset may result
in the possibility of lost messages.”

Regards, Bivas

LP server send me resend request to send messages( check tag 7 &
Tag 16 )

8=FIX.4.49=8135=249=blabla56=blabla34=138852=20100105-
05:43:34.1477=8716=010=083

I sent sequence reset-reset mode(not gapfill) higher than expected seq
num (plz chaeck tag 36)

8=FIX.4.49=5235=449=blabla56=blabla34=8743=Y52=1/5/2010
11:13:42123=N36=9110=33

but they again gives resend request

8=FIX.4.49=8135=249=blabla56=blabla34=138952=20100105-
05:43:41.8817=8716=010=087

How to handle this situation? Thanks in advance.

5

Hi, I noticed the following in your Seq-Reset message header:
“52=1/5/2010 11:13:42” timestamp not in UTC format.

Apart from this, are you trying to recover a session by sending a
sequence reset?

As per FIX4.4 Specs, vol-2, Pg-23, the sequence reset (Reset Mode
message should not be used in the scenario you depicted unless it is a
disaster recovery scenario.

To Quote the specs… “Sequence Reset – Reset should NOT be used as a
normal response to a Resend Request (use Sequence Reset – Gap Fill
mode). The Sequence Reset – Reset should ONLY be used to recover from a
disaster situation which cannot be recovered via the use of Sequence
Reset – Gap Fill. Note that the use of Sequence Reset – Reset may result
in the possibility of lost messages.”

Regards, Bivas

LP server send me resend request to send messages( check tag 7 &
Tag 16 )

8=FIX.4.49=8135=249=blabla56=blabla34=138852=20100105-
05:43:34.1477=8716=010=083

I sent sequence reset-reset mode(not gapfill) higher than expected seq
num (plz chaeck tag 36)

8=FIX.4.49=5235=449=blabla56=blabla34=8743=Y52=1/5/2010
11:13:42123=N36=9110=33

but they again gives resend request

8=FIX.4.49=8135=249=blabla56=blabla34=138952=20100105-
05:43:41.8817=8716=010=087

How to handle this situation? Thanks in advance.
I have also send gapfill message with new seq num=1(short seqnum) and high seqnum(for e.g. 200) but they again gives resend request one less than before i.e. from 7=88 to 16=0

6

[ original email was from Bivas Mishra - bivas.mishra@wipro.com ]
Resend request message is asking you to send messages from seq no 87 onwards. Your gapfill messages should be from above this range.

To quote the specs again:

“If the GapFillFlag field is present (and equal to “Y”), the MsgSeqNum should conform to standard message sequencing rules (i.e. the MsgSeqNum of the Sequence Reset GapFill mode message should represent the beginning MsgSeqNum in the GapFill range because the remote side is expecting that next message sequence number).”

Also, as mentioned by Taras, check if Tag 52 in your sending message constitutes a garbled message because it is not in UTC format.

Regards,
Bivas

I have also send gapfill message with new seq num=1(short seqnum) and
high seqnum(for e.g. 200) but they again gives resend request one less
than before i.e. from 7=88 to 16=0

Hi, I noticed the following in your Seq-Reset message header:
“52=1/5/2010 11:13:42” timestamp not in UTC format.

Apart from this, are you trying to recover a session by sending a
sequence reset?

As per FIX4.4 Specs, vol-2, Pg-23, the sequence reset (Reset Mode
message should not be used in the scenario you depicted unless it is a
disaster recovery scenario.

To Quote the specs… “Sequence Reset – Reset should NOT be used as a
normal response to a Resend Request (use Sequence Reset – Gap Fill
mode). The Sequence Reset – Reset should ONLY be used to recover from
a disaster situation which cannot be recovered via the use of Sequence
Reset – Gap Fill. Note that the use of Sequence Reset – Reset may
result in the possibility of lost messages.”

Regards, Bivas

LP server send me resend request to send messages( check tag 7 &
Tag 16 )

8=FIX.4.49=8135=249=blabla56=blabla34=138852=20100105-
05:43:34.1477=8716=010=083

I sent sequence reset-reset mode(not gapfill) higher than expected
seq num (plz chaeck tag 36)

8=FIX.4.49=5235=449=blabla56=blabla34=8743=Y52=1/5/2010
11:13:42123=N36=9110=33

but they again gives resend request

8=FIX.4.49=8135=249=blabla56=blabla34=138952=20100105-
05:43:41.8817=8716=010=087

How to handle this situation? Thanks in advance.