[Quickfix-users] same app: SocketInitiator works, SocketAcceptor fails (all on linux)
Brought to you by:
orenmnero
From: Alexey Z. <ale...@gm...> - 2006-08-25 13:30:38
|
Mark, It may happened if your initiator sends invalid (for you acceptor) TargetCompID. I think QF should report such things in the event log. Regards, Alexey Zubko qui...@li... wrote: > > Subject: > [Quickfix-users] same app: SocketInitiator works, SocketAcceptor fails > (all on linux) > From: > "Mark T. Kennedy" <mke...@di...> > Date: > Thu, 24 Aug 2006 14:36:31 -0400 > To: > qui...@li... > > To: > qui...@li... > > > i have an app that works as an initiator but fails as an acceptor. > when run as an acceptor, it receives the logon request from the > initiator and then immediately tears down the socket. nothing > is written to the acceptor's event log about this. the initiator > sees: > > 20060824-17:17:38 : Connection succeeded > 20060824-17:17:39 : Initiated logon request > 20060824-17:17:39 : Socket Error: Connection reset by peer. > 20060824-17:17:39 : Disconnecting > > i have strace'd the acceptor and have verified that the complete > logon message was received without error. > > there doesn't seem to be a way to turn on any kind of verbose > logging. > > thoughts/comments/suggestions? > > /mark kennedy > > > |