[Quickfix-developers] Orders never sent vs session vs startTime

[John G. <joh...@wa...>]

Hi,

Thanks to the list and Oren, I know that if I start writing orders to the
session before StartTime they will never be sent because QF relies on
the counterparty to ask for missing messages. So I took extra care about
the startTime parameter to be sure it would be set long before we actually
connect to the QF powered process to send the orders.

What happened yesterday was the following (in UTC times)

- startTime in config file: 04:30
- actual launch of process: 04:00 (yes I told them it's useless)
- immediate "Created Session" trace from the app which is just an 
std::cout from onCreate().
- but the counterparty was down. So QF goes and tries the 4
SocketConnectHostN it has available in config file and of course fails on
all of them and goes on cycling.
- at 05:44 we start sending orders to QF
- at 07:01 the counterparty comes up and logon succeeds
- all the previously sent orders have never been heard of again

I thought I understood that as long as I was sending orders to QF after 
StartTime, they would be sent when logon suceeded. What do I have wrong ? 
Is this related to the fail over (SocketConnectHost/Port) mechanism or my 
(mis)understanding of how QF works ? 

QF version is 1.11.1

We had talked some while ago about seperating a StartTime for the session 
and a "ConnectionTime" parameter, is this still something considered 
possible ? 

Thanks for any help/hints.
Sincerely,
JG