Re: [Quickfixj-users] Need help to make Failover work with QuickFIX/J

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

Hi,

sorry, I still don't get the problem.
So you have ONE initiator. And this initiator connects alternatively to "host" and "host1". I assume 
this happens on a connection disruption. It should not connect to "host1" as long as there is a 
connection to "host" established.
Or are you telling me that the initiator sends a Logon to "host" and "host1" at the same time?

Chris.


On 26/03/18 11:22, Rekha Hindlekar wrote:
>> Hello Christoph,
>>
>> I am planning to implement Failover,
>>
>> I run two instances of my FIX Acceptor application on two hosts viz.,*Host*and*Host_1*.
>>
>> I did configuration in Initiator Session by specifying **/*SocketConnectHost=Host */and 
>> /*SocketConnectHost1=Host_1*(and specified corresponding ports).///
>>
>> I ran all the applications i.e. Initiator and Acceptor on both hosts, initially Initiator got 
>> connected to Acceptor running on/*Host.*/
>> /Now when I shut the Acceptor running on /*Host*//, sessions were established with /Acceptor 
>> running on*Host_1*.///
>> ///
>> ///
>> ///When I restarted the Acceptor running on/*Host*, then Logon request from the Initiator was 
>> alternately sent to both the Acceptors running*Host*/and /*Host1*.//////
>
>
> On Mon, Mar 26, 2018 at 2:05 PM, Christoph John <chr...@ma... 
> <mailto:chr...@ma...>> wrote:
>
>     Hi,
>
>
>>     This observation is not according to that noted in the documentation URL.
>
>     Which documented behaviour do you mean? The documentation you mentioned is about Acceptors and
>     does not talk about any behaviour regarding Initiators.
>
>     What is the exact problem that you're having?
>
>     Chris.
>
>

-- 
Christoph John
Development & Support
T +49 241 557080-28
chr...@ma...

MACD GmbH
Oppenhoffallee 103
D-52066 Aachen
www.macd.com

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