Why does QuickfixJ still initiate logon after sending logout response

Question

I'm using QuickfixJ to connect to the counter party for FIX message.

However, some day I found the log is as follow:

-20:59:39: Received logout request: Initiating logout
-20:59:39: Sent logout response
-20:59:39: Initiated logon request
-20:59:45: Initiated logon request
-20:59:50: Initiated logon request
-20:59:55: Initiated logon request
-21:00:00: Initiated logon request

Apparently, counter party sent a logout request and my app responded. The session should be finished and closed.

Why the app still trying to initiate a logon request to counter party?

Am I missing something? Because I have no implementation within onLogout(SessionId session) and fromAdmin(Message message, SessionId session) and I thought it could be automatically handled by QuickfixJ itself

Answer 1

That's how QF works. If the connection goes down but you're still within the session's active schedule, it tries to reconnect.

It won't stop trying to reconnect until EndTime. Then it sleeps until the next StartTime.

Answer 2

It depends whats in your cfg file as ReconnectInterval

[default]
ReconnectInterval=5

and I think it depends on what's in

public void onLogout(SessionID sessionID) {        
    observableLogon.logoff(sessionID);
}

with the reconnects used in case the disco was unexpected or unintended