[QFJ-15] Connect/reconnect generates phony error during seqnum resync Created: 25/May/06  Updated: 15/Nov/12  Resolved: 26/May/06

Status: Closed
Project: QuickFIX/J
Component/s: Engine
Affects Version/s: 1.0.0 B3
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Colin Ruthven Assignee: Steve Bate
Resolution: Not a bug Votes: 0
Labels: None
Environment:

RedHat Linux Enterprise 4, JDK 1.4.2_09. x86 architecture.



 Description   

Sequence -
1) Send order (Limit)
2) Drop connection
3) Order executes in series of parials
4) Reconnect
5) Sequence number resend/reset messages are exchanged interleaved with execution reports
6) The Application is passed the execution reports as if no error occurred

The final execution report is passed to the application, but a rejection is sent to the initiator complaining that Tag 122 is missing. Execution report is not required to have Tag 122 and the previous message received did have Tag 122.
This happens each time this test is repeated. Sometimes the last two messages preceding are execution reports and both are rejected.
Log excerpt from the reconnect follows -
8=FIX.4.2^A9=67^A35=A^A34=5811^A49=direct3^A52=20060524-18:58:49.012^A56=direct4^A98=0^A108=30^A10=225^A
8=FIX.4.2^A9=67^A35=A^A34=5812^A49=direct3^A52=20060524-18:59:14.928^A56=direct4^A98=0^A108=30^A10=235^A
8=FIX.4.2^A9=0105^A35=A^A34=007202^A43=N^A52=20060524-19:00:00^A49=direct4^A56=direct3^A98=0^A108=30^A6272=BOX/OPT,PHLX/OPT^A6273=BOX/OPT^A10=110^A
8=FIX.4.2^A9=0073^A35=2^A34=007203^A43=N^A52=20060524-19:00:00^A49=direct4^A56=direct3^A7=5811^A16=5812^A10=069^A
8=FIX.4.2^A9=71^A35=2^A34=5813^A49=direct3^A52=20060524-18:59:15.027^A56=direct4^A7=7201^A16=99999^A10=183^A
8=FIX.4.2^A9=0285^A35=8^A34=007201^A43=Y^A52=20060524-19:00:00^A49=direct4^A56=direct3^A37=00000015.00003b5b.4474a8c6.0001^A11=000000004159467^A17=00002b0c.88e7d58a.01.01^A150=1^A20=0^A39=1^A55=F^A54=1^A100=NYSE^A207=NYSE^A38=500^A44=7^A32=100^A30=NYSE^A31=7^A14=100^A151=400^A6=7^A167=CS^A1=U515^A60=20060524-18:59:59^A40=2^A59=1^A204=1^A10=067^A
8=FIX.4.2^A9=0094^A35=4^A34=007202^A43=Y^A52=20060524-19:00:00^A49=direct4^A56=direct3^A122=20060524-19:00:00^A123=Y^A36=7204^A10=109^A
8=FIX.4.2^A9=0073^A35=2^A34=007204^A43=N^A52=20060524-19:00:00^A49=direct4^A56=direct3^A7=5813^A16=5813^A10=073^A
8=FIX.4.2^A9=0285^A35=8^A34=007205^A43=N^A52=20060524-19:00:02^A49=direct4^A56=direct3^A37=00000015.00003b5b.4474a8c6.0001^A11=000000004159467^A17=00002b0c.88e7d58c.01.01^A150=1^A20=0^A39=1^A55=F^A54=1^A100=NYSE^A207=NYSE^A38=500^A44=7^A32=100^A30=NYSE^A31=7^A14=200^A151=300^A6=7^A167=CS^A1=U515^A60=20060524-19:00:02^A40=2^A59=1^A204=1^A10=039^A
8=FIX.4.2^A9=96^A35=4^A34=5811^A43=Y^A49=direct3^A52=20060524-18:59:25.415^A56=direct4^A122=20060524-18:59:25^A36=5813^A123=Y^A10=167^A
8=FIX.4.2^A9=96^A35=4^A34=5813^A43=Y^A49=direct3^A52=20060524-18:59:25.478^A56=direct4^A122=20060524-18:59:25^A36=5814^A123=Y^A10=179^A
8=FIX.4.2^A9=71^A35=2^A34=5814^A49=direct3^A52=20060524-18:59:25.482^A56=direct4^A7=7203^A16=99999^A10=192^A
8=FIX.4.2^A9=0094^A35=4^A34=007203^A43=Y^A52=20060524-19:00:11^A49=direct4^A56=direct3^A122=20060524-19:00:11^A123=Y^A36=7205^A10=115^A
8=FIX.4.2^A9=0285^A35=8^A34=007205^A43=Y^A52=20060524-19:00:11^A49=direct4^A56=direct3^A37=00000015.00003b5b.4474a8c6.0001^A11=000000004159467^A17=00002b0c.88e7d58c.01.01^A150=1^A20=0^A39=1^A55=F^A54=1^A100=NYSE^A207=NYSE^A38=500^A44=7^A32=100^A30=NYSE^A31=7^A14=200^A151=300^A6=7^A167=CS^A1=U515^A60=20060524-19:00:02^A40=2^A59=1^A204=1^A10=050^A
8=FIX.4.2^A9=107^A35=3^A34=5815^A49=direct3^A52=20060524-18:59:25.643^A56=direct4^A45=7205^A58=Required tag missing^A371=122^A372=8^A373=1^A10=081^A



 Comments   
Comment by Steve Bate [ 26/May/06 ]

Hello Colin,

The FIX 4.2 specification states that OrigSendingTime (tag=122) is "required for messages resent as a
result of a ResendRequest". In other words, any message with 43=Y should have a tag 122. Are the
execution reports being sent from a QuickFIX/J engine? QFJ should be filling in this field
automatically.

Steve

Comment by Colin Ruthven [ 26/May/06 ]

The target is a home grown system.

I'll let them know.

I take it then that my app processed the first occurrence of the message and QuickFIX/J threw away the second one and complained about the missing tag 122?

Please close this issue.

Thanks, Colin

Generated at Sat Nov 23 00:39:42 UTC 2024 using JIRA 7.5.2#75007-sha1:9f5725bb824792b3230a5d8716f0c13e296a3cae.