Re: [Quickfixj-users] outgoing seqnum

[Steve B. <st...@te...>]

> We had to stop our engine mid-day today to do some database 
> maintenance.  ...
>
> 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?  

I don't know based on the information you've provided. You
say you were doing database maintenance. If the engine's
database connection was bad it might explain the problem.
You'd see information in the log file and/or event log
table if this was the cause. This could happen if the
database was restarted but the FIX engines were not.

Was the outgoing sequence number = 1 in the sessions table?
This information won't help to explain the lack of updates,
but it will tell me if the session was reset or whether the
engine just couldn't read the information from the database.

> 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?  

I'd be surprised is this was an issue directly related to
stopping and starting the engine midday. Set up a client
and server test environment using a JDBC message store and
try stopping and starting. It should work. I don't personally
use the JDBC message store, but there are tests for the
implementation and others use it. There are no bug reports
related to this type of behavior.

> 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?  

Based on the information so far, I'd guess not. Check the log
files for additional clues. 

> 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?

You just be able to restart. If you have any other information,
please let us know.

Steve