[Quickfixj-users] outgoing seqnum

[Robert B. <rbr...@me...>]

Hey guys,

We had to stop our engine mid-day today to do some database maintenance.
This is the first time we did this.  It properly sent out a logout
message to our endpoint and shutdown the engine gracefully.  We are
using jdbc logging.  We fired the engine back up about an hour and a
half later and the engine started a new session and started BOTH
incoming and outgoing sequence numbers back at 1.  This caused our FIX
to start a seqnum loop with our endpoint...we would send them 1 and they
would send us that we should be sending 905.  The next heartbeat would
show we sent them 2 and that we should have sent them 905...and so
forth.  You can see the problem...we'd have to wait 903 more iterations
at 30 seconds a pop before the engine would have iterated back up to a
sequence number worthy of receiving messages from our endpoint.  We
looked at the session table from the jdbc looging and the engine does
not seem to be updating this table each time the outgoing sequence
number, so when we stop and start the engine it starts from 1 every
time.  We have NOTHING in our configuration file that tells the engine
to always start from 1...I know there are config parameters that allow
for this...but we are not using any of them...our config file is bare
bones...ip, port, start and stop times, sender and target ids, fix
version...nothing else aside from the jdbc logging config params also.=20=
=20

Why is the sessions table not being updated each time the outgoing seq
num is being incremented by the engine?  Why is this not being
maintained?  If we need to stop and start the engine in the middle of
the day, we obviously don't want this to happen every time.  What can we
do?  In this instance, we contacted the endpoint and they reset the seq
num on their end so we could catch up to a reasonable number and then we
captured all missed messages. Is there a bug in the jdbc logging?=20=20

Any thoughts on what we can do to better handle a mid-day shutdown and
restart that would allows us to pick back up where we left off with our
endpoint?

Thanks,
rob

Merlin Securities - #1 Prime Broker North America, #1 Prime Broker Single S=
trategy Funds, #1 Prime Broker Funds Under $100M - Global Custodian 2007


=20

--------------------------------------------------------

This message contains information from Merlin Securities, LLC, or from one =
of its affiliates, that may be confidential and privileged. If you are not =
an intended recipient, please refrain from any disclosure, copying, distrib=
ution or use of this information and note that such actions are prohibited.=
 If you have received this transmission in error, please notify the sender =
immediately by telephone or by replying to this transmission.
=20
Merlin Securities, LLC is a registered broker-dealer. Services offered thro=
ugh Merlin Securities, LLC are not insured by the FDIC or any other Federal=
 Government Agency, are not deposits of or guaranteed by Merlin Securities,=
 LLC and may lose value. Nothing in this communication shall constitute a s=
olicitation or recommendation to buy or sell a particular security.