Re: [Quickfix-users] Resend Request

[ka w. <ka...@gm...>]

I think I found part of the problem.
The vendor sent me a resendRequest with a BeginSeqNo=2968 and EndSeqNum=0.
In log4FIX, on the message 2968, I can read "Message Errors
(NewOrderSingle): Actual body length=190, Expected body length=199".
- What should I do if a body length is not the one expected?
- How this could have happened?
- is it normal that QFIX didn't take any action after the resendRequest?
- is there anything that I should have done?

Thanks,
Kamel

2010/3/10 Kenny Stone <ks...@co...>

> QuickFIX Documentation:
> http://www.quickfixengine.org/quickfix/doc/html/index.html
> QuickFIX Support: http://www.quickfixengine.org/services.html
>
>
> Are you sure there was no reject from your app?
>
> Can you replicate this in your vendor's test environment?
>
> Can you replicate using the exact resend request string the vendor sent and
> a fixtest <http://github.com/quickfix/quickfix/tree/master/test/>?
>
> --
> Kenny Stone
> Connamara Systems, LLC
>
>
> On Wed, Mar 10, 2010 at 9:56 PM, ka wone <ka...@gm...> wrote:
>
>> QuickFIX Documentation:
>> http://www.quickfixengine.org/quickfix/doc/html/index.html
>> QuickFIX Support: http://www.quickfixengine.org/services.html
>>
>>
>> Hi,
>>
>> Into production today we received a resend request. Unfortunately and as a
>> surprise QFix didn't take any of the following actions (extract of the FIX
>> specs):
>>
>> "Upon receipt of a Resend Request, the resender can respond in one of
>> three ways:
>> 1. retransmit the requested messages (in order) with the original sequence
>> numbers and
>> PossDupFlag set to “Y”
>> 2. issue a SeqReset-GapFill with PossDupFlag set to “Y” message to replace
>> the retransmission
>> of administrative and application messages
>> 3. issue a SeqReset-Reset with PossDupFlag set to “Y” to force sequence
>> number
>> synchronization."
>>
>> I know that QFIX should by default adopt the solution 1. I have tested
>> this with a simple Initiator/Acceptor project and QFix behaves correctly
>> without even putting *SendRedundantResendRequests =Y.*
>> Moreover I know that all requested messages are present in the BODY file.
>>
>> But here is the problem. How this could have happened into production?
>> Does anyone has experienced the same problem?
>> Does putting *SendRedundantResendRequests =Y could help on anything?*
>>
>> Thanks,
>> Kamel
>>
>>
>> ------------------------------------------------------------------------------
>> Download Intel&#174; Parallel Studio Eval
>> Try the new software tools for yourself. Speed compiling, find bugs
>> proactively, and fine-tune applications for parallel performance.
>> See why Intel Parallel Studio got high marks during beta.
>> http://p.sf.net/sfu/intel-sw-dev
>> _______________________________________________
>> Quickfix-users mailing list
>> Qui...@li...
>> https://lists.sourceforge.net/lists/listinfo/quickfix-users
>>
>>
>
>
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Quickfix-users mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-users
>
>