[Quickfix-developers] Question about HeartBeats and Logouts

[Bernard S. <bsp...@gx...>]

Folks,

	I am experimenting with QuickFix, and I have a couple of questions.  I have
created a CLIENT (initiator) and a SERVER (acceptor) which both run on the
same machine.  Each is a simple application that does nothing other than
display a message when each of the Application member functions is called.
Basically, all they do is instantiate an initiator (or acceptor) with the
appropriate parameters, and start it.  The onRun() just sleeps in an
infinite loop.  ReconnectInterval is 20, and HeartBeatInterval is 30 for
both.

	I expect to see onCreate() called on both applications, which I do.  Next,
I expect to see onLogon() called for both, which I eventually do.  After
that, I guess I expect to see an exchange of heartbeats and nothing else.
Instead, after about 30 seconds, onLogout() is called on both CLIENT and
SERVER, followed by repeated calls to onLogon() and onLogout().  Looking at
the message log, I see repeated logon messages, occasionally a resend
request, and very rarely a heartbeat message.

	My questions are as follows:

1) Am I expecting the right thing?
2) Does the Engine handle heartbeats, or does my application have to
generate heartbeats itself?
3) I delete files in the log directory each time before I restart.  Why does
onLogon() sometimes get called immediately, and sometimes take 20 seconds or
so to get called?
4) Why does onLogout() get called at all?  Shouldn't the session remain
logged in indefinitely?
5) Why do the .message log files in my log directory periodically get wiped
clean (size goes to 0).

I'd appreciate any help or insight.  Thanks.

------------------------------------------
Bernard Spanger
bsp...@gx...
G. X. Clarke & Co.
10 Exchange Place
Jersey City, NJ 07302
201-200-3607