|
From: John P. <joh...@ho...> - 2009-01-05 14:48:01
|
Hi Jim, I am not sure I understand what particular problem you are trying to deal with. If you used QFJ JMX agents before, esp. the quickfix/j mbean, you should know that QFJ does provide a nice way of managing session sequence online, and remotely if you will. As for the scenario that Jan desribed, it can be easily addressed by bundling a command to remove (or relocate if you want to keep) the file-store in the "start of day" start up script. This way, the seq no.s are always reset at the start of each day. For intra-day re-start however, you don't want to reset the seq no of course. Personally, I think QFJ did a pretty good job in this area. John jim_b_o wrote: > > > John Peng wrote: >> >> - While your session is alive, you can use JMX via JConsole to manage the >> seq no. >> - When the engine is off, you can clean up the filestore to reset the seq >> no for next session. >> > > I think we need a mechanism that allows us to reset the seq no (and any > relevant stores) that is consistent with the FIX Protocol recommendations, > i.e. by sending a Logon with ResetSeqNumFlag=Y after a TestRequest and > Heartbeat response including any required resends, within an already > established connection. Only this way can we ensure recovery of a failed > session prior to resetting the seq no. > > As Jan Pevzner suggests, this would be a dynamic mechanism, invoked when > desired (probably at a particular time of day). The various ResetOnXXX > settings do not allow for proper session recovery. > -- View this message in context: http://n2.nabble.com/Managing-SeqNo-manually-tp2095579p2113153.html Sent from the QuickFIX/J mailing list archive at Nabble.com. |