|
From: Vipin C. <vip...@gm...> - 2018-01-11 11:08:43
|
looks this is same scenario reported recently as well. I think you can watch pull request https://github.com/quickfix-j/ quickfixj/pull/152 Thanks Vipin On Thu, Jan 11, 2018 at 3:09 PM, Muhammadh Aadhil <mua...@gm...> wrote: > QuickFIX/J Documentation: http://www.quickfixj.org/documentation/ > QuickFIX/J Support: http://www.quickfixj.org/support/ > > > Hi All, > > First of all, I'm very new to this forum, if anyone helps me i'll be very > grateful to you guys. > > In an Initiator Session, we do have 2 different SocketConnectHost for Fail > over scenario. With this configuration, we are connected to the sending a > manual Logout request to the session and sending a Logon request. When we > try this scenario, Application tries to logon to the Secondary > Ip(SocketConnectHost1). Our expectation is to continue the Primary > IP(SocketConnectHost). > > [session] > SessionIdentifier=TDWL > ConnectionType=initiator > SenderCompID=SLGM0 > TargetCompID=TDWL > SessionQualifier=TDWL > SocketConnectHost=127.0.0.1 > SocketConnectPort=7000 > SocketConnectHost1=192.168.13.40 > SocketConnectPort1=7000 > HeartBtInt=20 > StartTime=09:20:00 > EndTime=23:15:00 > > > > -- > Sent from: http://quickfix-j.364392.n2.nabble.com/ > > ------------------------------------------------------------ > ------------------ > 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 > |