|
From: Christoph J. <chr...@ma...> - 2020-04-30 10:00:16
|
Hi, did you change QFJ version or why do you think it is QFJ related? Do you only have one FIX session? If not, do all sessions show this behaviour? (apart from that, the TCP/IP stuff is done via the MINA framework and not within QFJ itself) This message appears when the initiator side of the connection considers the connection broken and tries to reconnect. But the acceptor still considers it a vital connection (probably until the connection timeout kicks in). From my experience this happens mostly on VPN connections via internet. Reasons for this were one of: - different MTU sizes on both sides of the connection or on a router/firewall in between - asymmetric routing - differing VPN parameters leading to different rekeying behaviour on both ends of the connection. Hope that helps, Chris. On 30.04.20 05:51, Vipin Chaudhary wrote: > QuickFIX/J Documentation: http://www.quickfixj.org/documentation/ > QuickFIX/J Support: http://www.quickfixj.org/support/ > > > > Hi Team, > > We are facing strange issue with quickfixj. > > We are SessionAcceptor, sometime when initiator disconnect, then quickfixj is not able to > recognize the disconnection. So when client logon next time it say > " Multiple logons/connections for this session are not allowed". > Although in reality client is disconnected. > Earlier it was very rare and happening once in a while but nowadays its happening like once in week. > Quickfixj is not able to recover from this and we need to restart our application > > *Do anyone have seen/fix this ?* > > Thanks > Vipin Chaudhary > > > _______________________________________________ > 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 |