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

[Rekha H. <rek...@or...>]

Hello All,

Any leads..

On Tue, Mar 27, 2018 at 11:16 AM, Rekha Hindlekar <
rek...@or...> wrote:

> Hello All,
>
> I have attached the work flow. If its round robin then how can we prevent
> sending login request to both hosts from initiator.
> Since initiator and acceptor both are developed by us using quickfix/j
>
> On Mon, Mar 26, 2018 at 7:30 PM, Øyvind Matheson Wergeland <
> oyv...@om...> wrote:
>
>> QuickFIX/J Documentation: http://www.quickfixj.org/documentation/
>> QuickFIX/J <http://www.quickfixj.org/documentation/QuickFIX/J> Support:
>> http://www.quickfixj.org/support/
>>
>>
>>
>> The QF/J initiator will try to connect to the configured endpoints round
>> robin. I guess this is the behavior you see.
>>
>>  -Øyvind
>>
>> 26. mar. 2018 kl. 12:21 skrev Christoph John via Quickfixj-users <
>> qui...@li...>:
>>
>> QuickFIX/J Documentation: http://www.quickfixj.org/documentation/
>> QuickFIX/J Support: http://www.quickfixj.org/support/
>>
>>
>> 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...>
>> 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 557...@ma...
>>
>> MACD GmbH
>> Oppenhoffallee 103
>> D-52066 Aachenwww.macd.com
>>
>> Amtsgericht Aachen: HRB 8151
>> Ust.-Id: DE 813021663
>> Geschäftsführer: George Macdonald
>>
>> ------------------------------------------------------------
>> ------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>
>> _______________________________________________
>> Quickfixj-users mailing list
>> Qui...@li...
>> https://lists.sourceforge.net/lists/listinfo/quickfixj-users
>>
>>
>> ------------------------------------------------------------
>> ------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Quickfixj-users mailing list
>> Qui...@li...
>> https://lists.sourceforge.net/lists/listinfo/quickfixj-users
>>
>>
>
>
> --
> Regards
>
> Rekha Hindlekar  |  Sr. Technical Lead  |  OroSoft Solutions Pvt. Ltd.
> rek...@or... | www.orosoftsolutions.com
> <http://www.orosoftsolutions.com>
>
> DISCLAIMER:
>
> "This e-mail message including any of its attachments is intended solely
> for the addressee(s) and may contain privileged information. If you are not
> the addressee or you have received this email message in error, please
> notify the sender who will remove your details from its database. You are
> not authorized to read, copy, disseminate, distribute or use this e-mail
> message or any attachment to it in any manner and must delete the email and
> destroy any hard copies of it.
>
> This e-mail message does not contain financial instructions or commitments
> of any kind. Any views expressed in this message are those of the
> individual sender and do not necessarily reflect the views of OroSoft
> Solutions Pvt. Ltd., or any other related subsidiaries, entities or
> persons."
>



-- 
Regards

Rekha Hindlekar  |  Sr. Technical Lead  |  OroSoft Solutions Pvt. Ltd.
rek...@or... | www.orosoftsolutions.com
<http://www.orosoftsolutions.com>

DISCLAIMER:

"This e-mail message including any of its attachments is intended solely
for the addressee(s) and may contain privileged information. If you are not
the addressee or you have received this email message in error, please
notify the sender who will remove your details from its database. You are
not authorized to read, copy, disseminate, distribute or use this e-mail
message or any attachment to it in any manner and must delete the email and
destroy any hard copies of it.

This e-mail message does not contain financial instructions or commitments
of any kind. Any views expressed in this message are those of the
individual sender and do not necessarily reflect the views of OroSoft
Solutions Pvt. Ltd., or any other related subsidiaries, entities or
persons."