[Quickfix-developers] Expected response to second Logon request?
Brought to you by:
orenmnero
|
From: Derek K. <DK...@li...> - 2006-06-23 17:26:12
|
I have a situation with QuickFIX 1.10.2 (FIX 4.2) where the initiator sending two Logon (35=A) requests. The first (expected) Logon arrives and the session begins normally. Then, later in the day, for reasons I have no controller over, the acceptor sends a SECOND unexpected Logon request without a preceding Logout. QuickFIX doesn't like this second Logon. It replies by saying "Logon state is not valid for message" followed by "Dropped Connection." It generates a Logout event and ends the session. My client (the initiator) is saying other FIX engines she connects do not behave this way when they get a second Logon -- they just output a warning or ignore the second Logon altogether. Can anyone tell me where in the FIX spec this behavior is defined? I'm trying to figure out if this is a QuickFIX bug or the correct FIX response to a second Logon. Thanks. Derek |