Re: [Quickfix-developers] QuickFix Logon

[Oren M. <or...@qu...>]

There is no guarantee that your session will be logged on immediately  
after calling start().  In fact, it is rather unlikely.

How have you confirmed that onLogon is being invoked before you call  
isLoggedOn()?  Have you also confirmed you were not subsequently  
logged off? (Are you monitoring onLogout?)

isLoggedOn and onLogon are intimately related.  The code within the  
session to invoke onLogon is:

   if ( isLoggedOn() )
     m_application.onLogon( m_sessionID );

So by definition it is not possible for onLogon to be invoked unless  
at some point isLoggedOn returns true.

isLoggedOn will return false if either sentLogon() or recevedLogon()  
return false.  Can you confirm that either of these return false as  
well?

--oren

> In our application, sometimes we get Session.lookupSession 
> (sessionID).isLoggedOn() returning false value after calling  
> initiator.start(),  onLogon(SessionID sessionID) be triggered and  
> even receiving heartbeat.  Can anyone explain to me what should  
> cause this function returning false?