Re: [Quickfixj-users] Message Resliency On FIX Initiator side

[Christoph J. <chr...@ma...>]

Hi,

what do you mean by "how it can be tested"? Pull the network cable?? ;) Alternatively you could ask 
the other side to kill their Acceptor.
The expectation would be that the remote side gets all missing messages by re-requesting them via 
ResendRequest on the next Logon.

Cheers,
Chris.

On 15/10/18 13:48, Rahul Gaur wrote:
> QuickFIX/J Documentation: http://www.quickfixj.org/documentation/
> QuickFIX/J Support: http://www.quickfixj.org/support/
>
>
>
>
> Hi All,
>
> We have a typical FIX setup in which we have one Initiator connecting to an external Acceptor and 
> are exchanging FIX messages with each other. On *Initiator *side we are using *FileStoreFactory 
> *as MessageFactory and caching 10000 outgoing messages. We need to test a resiliency scenario 
> wherein the Acceptor goes down while some of the messages from Initiator are still in-flight. Can 
> you suggest how it can be tested and also what is the expectation in the above scenario.
>
> The quickfixj version on initiator side is *1.6.3*
>
> Thanks
> Rahul
>
>
>
>
>
> _______________________________________________
> Quickfixj-users mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfixj-users

-- 
Christoph John
Software Engineering
T +49 241 557080-28
chr...@ma...

MACD GmbH
Oppenhoffallee 103
52066 Aachen, Germany
www.macd.com

Amtsgericht Aachen: HRB 8151
Ust.-Id: DE 813021663
Geschäftsführer: George Macdonald