SocketInitiator.Stop() does not take into account sessions that have not logged on yet

[PetteriPertola]

Hi,

I'm calling IInitiator.Stop() (using SocketInitiator) in some cases where we need to disconnect all sessions. This works fine if the sessions have at some point during the application lifecycle logged on successfully (OnLogon callback observed).

However, if a session has not yet connected since application start (for example the counterpart is down for a prolonged period of time), calling IInitiator.Stop() will not affect those sessions.

Instead, the configured sessions will continue to attempt to logon using 35=A indefinitely according to the configured StartTime and EndTime settings in the config.

I think this looks like a bug because I would expect the sessions to permanently disconnect at this point. Otherwise, while my initiator should be stopped, if the counterpart returns online, I will have an unexpected live session.

To reproduce: try to connect to a counterpart where the socket connection is established so 35=A logon is sent, but connection is forcibly closed by remote host without 35=Z or 35=A sent back, and then call Initiator.Stop().