{{Quickfixn}} capturing rejected messages

[Grant Birchmeier]

35=j is NOT a session reject, you can catch that with a regular OnMessage
callback.

35=3 is a session reject.  It happens under the application layer.  If one
of these happens, you probably have a code error or a misbehaving
counterparty.  You should not attempt to handle this in your application
layer.

Catching 35=3 is not supported in QF/n (or in the original QF/C++ either I
believe), because of the above reasons.  They should be rare, and I suggest
using log monitor to watch for them so that a developer can investigate
them when they occur.

On Wed, Sep 9, 2015 at 2:43 PM, Operations @ ChaosMetrix <
operations at chaosmetrix.com> wrote:

> QuickFixJ seems to have a way to do this:
>
>
> http://stackoverflow.com/questions/19930938/handling-fix-reject-retrieve-fix-message-by-sequence-number-in-refseqnum-using
>
> On Wed, Sep 9, 2015 at 12:37 PM, Operations @ ChaosMetrix <
> operations at chaosmetrix.com> wrote:
>
>> Please provide instructions for accessing the original rejected message
>> when a session level reject occurs (35=3 or 35=j)
>>
>> thanks!
>>
>> _______________________________________________
>> Quickfixn mailing list
>> Quickfixn at lists.quickfixn.com
>> http://lists.quickfixn.com/listinfo.cgi/quickfixn-quickfixn.com
>>
>>
>
> _______________________________________________
> Quickfixn mailing list
> Quickfixn at lists.quickfixn.com
> http://lists.quickfixn.com/listinfo.cgi/quickfixn-quickfixn.com
>
>


-- 
Grant Birchmeier
*Connamara Systems, LLC*
*Made-To-Measure Trading Solutions.*
Exactly what you need. No more. No less.
http://connamara.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.quickfixn.com/pipermail/quickfixn-quickfixn.com/attachments/20150909/b9a53152/attachment-0001.htm>