Re: [Quickfixj-users] Sending a Heartbeat

[Marcassoli, S. <Sta...@gs...>]

Thanks Toli,
I think you might be correct. The message that the Source is expecting
on connection is:
1:16:13.653RX8=3DFIX.4.4|9=3D79|35=3D0|34=3D2|49=3DAAAA|52=3D20080420-15:=
16:13.652|5
6=3DBBB|1
12=3DL.0001.0002.0003.151613|10=3D120|=20

All this information should be available from the setting file.  Is
there a way that I can up quickfix logging so that I can see if it sends
this message?

Thanks,
Stacy
----------------------------------------------------------------------

Message: 1
Date: Tue, 24 Apr 2007 00:18:06 -0700
From: "Toli Kuznets" <to...@ma...>
Subject: Re: [Quickfixj-users] Sending a Heartbeat
To: qui...@li...
Message-ID:
	<406...@ma...>
Content-Type: text/plain; charset=3DISO-8859-1; format=3Dflowed

Stacy,

I may be mistaken, but I think all  heartbeat exchange happens behind
the scenes automatically.

Once you log on to your FIX acceptor and they exchange login messages,
each side sends heartbeats to each other automatically.

if that's not enough for yo, you can try sending a heartbeat in the
onLogon() method in your FIX Application subclass as well.

for example, when our Marketcetera OMS connects to the FIX exchange
simulator (essentially the ordermatcher in the quickfixj examples
directory), the simulator sends a heartbeat to OMS after logon, and the
OMS replies. and it's the underlying QFJ layer that handles all of that,
we didn't have to add any code to setup heartbeat exchange, aside from
having the default HeartBtInt=3D30 value setup in the config file (ours =
is
done in Spring but it's the same idea):
http://trac.marketcetera.org/trac.fcgi/browser/platform/trunk/oms/src/ma
in/resources/quickfixj.xml

hope this helps.