|
From: Christoph J. <chr...@ma...> - 2018-06-08 14:45:58
|
AFAIK FIX itself has no concept of session time. Maybe your counterparty's FIX session does not support the definition of start and end time. But if you agreed with them that a new session will start at a defined time then they should set up a cronjob or whatever to have their session reset then. Maybe double check that their time is equal to your time. E.g. we once had a problem with Bloomberg where the session was reset after a disconnection during the day and it turned out that they had configured a different time zone. Your proposed solution seems to be fine. Cheers, Chris. On 08/06/18 03:10, Robert Nicholson wrote: > QuickFIX/J Documentation: http://www.quickfixj.org/documentation/ > QuickFIX/J Support: http://www.quickfixj.org/support/ > > > We don’t want to configure 141=Y on every logon but my counterparty seems to only reset if I’m logged on at the time of the reset > and not at any particular agreed schedule. My understanding is that quickfixj will logoff at session end and my counterparty isn’t > expecting this. > > So should they reset at the agreed time whether I’m logged on or not and accept the sequence number I send on my next logon? > > They seem to need to coordinate a logout before they will recognize a reset. > > Session is daily. > > I’m likely to have to trap a logon when nextsenderseqnum is 1 via toAdmin and add 141=Y since I do not want to reset on every logon. -- Christoph John Software Engineering T +49 241 557080-28 chr...@ma... MACD GmbH Oppenhoffallee 103 52066 Aachen, Germany www.macd.com Amtsgericht Aachen: HRB 8151 Ust.-Id: DE 813021663 Geschäftsführer: George Macdonald |