From: Steve B. <sb...@sm...> - 2006-02-17 09:02:51
|
Hi Chris, Is the ResetOnLogout session option what you want? You would logout using your local Session object which would=20 send a logout message to the other process. The logout would=20 cause a reset of the message store (resend log and sequence=20 numbers) in the remote session if the option above is enabled in it's settings. This would mean you can't logout the session /without/ starting a new logical session. Is that a problem in your case? Steve Bate Smart Trade Technologies Phone: +33 4 42 90 03 97 http://www.smart-trade.net/ > -----Original Message----- > From: qui...@li...=20 > [mailto:qui...@li...] On Behalf=20 > Of Chris van Ophuijsen > Sent: Friday, February 17, 2006 3:17 AM > To: qui...@li... > Subject: [Quickfix-users] How can I EOD with quickfix/j initiator >=20 > QuickFIX Documentation:=20 > http://www.quickfixengine.org/quickfix/doc/html/index.html > QuickFIX Support: http://www.quickfixengine.org/services.html >=20 > How can I programmatically send a message to the Session to=20 > abandon the connection, dump data, and reset sequences to 1=20 > in quickfix/j? >=20 > I am using head revision from Feb 12, using the mina libraries. >=20 > I would like to send a message from my program to disconnect=20 > and prepare to begin a fresh session.=20 >=20 >=20 >=20 > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep=20 > through log files for problems? Stop! Download the new AJAX=20 > search engine that makes searching your log files as easy as=20 > surfing the web. DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D230486& > dat=3D121642 > _______________________________________________ > Quickfix-users mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfix-users >=20 |
From: Steve B. <sb...@sm...> - 2006-02-17 14:36:02
|
Hi Oren, Yes, that's a good option. Do a logout and then set ResetSeqNum=3DY=20 when sending the next logon message. Chris, would that work better for you? > -----Original Message----- > From: qui...@li...=20 > [mailto:qui...@li...] On Behalf=20 > Of Oren Miller > Sent: Friday, February 17, 2006 3:03 PM > To: Chris van Ophuijsen > Cc: qui...@li... > Subject: Re: [Quickfix-users] How can I EOD with quickfix/j initiator >=20 > QuickFIX Documentation:=20 > http://www.quickfixengine.org/quickfix/doc/html/index.html > QuickFIX Support: http://www.quickfixengine.org/services.html >=20 > Steve, >=20 > Does QuickFIX/J support the ResetSeqNum field? >=20 > --oren >=20 > Chris van Ophuijsen wrote: >=20 > >QuickFIX Documentation:=20 > >http://www.quickfixengine.org/quickfix/doc/html/index.html > >QuickFIX Support: http://www.quickfixengine.org/services.html > > > > =20 > > > >>Hi Chris, > >> > >>Is the ResetOnLogout session option what you want? You would logout=20 > >>using your local Session object which would send a logout=20 > message to=20 > >>the other process. The logout would cause a reset of the=20 > message store=20 > >>(resend log and sequence > >>numbers) in the remote session if the option above is=20 > enabled in it's=20 > >>settings. This would mean you can't logout the session /without/=20 > >>starting a new logical session. Is that a problem in your case? > >> =20 > >> > > > > =20 > > Steve, > > > > Thanks for the reply. This is handy information, but a little less=20 > >than a perfect solution for me. I was hoping to be able to=20 > trigger an=20 > >EOD from an option on my client app as I am doing alot of=20 > testing with=20 > >re-sequencing against an acceptor type app and only need to=20 > EOD about=20 > >half of the time. Maybe setting the option to true and=20 > killing my app=20 > >uncleanly when I don't want to EOD will be a good workaround for me. > > > >Thanks for your help, > >Chris > > > > > > > > > > > >------------------------------------------------------- > >This SF.net email is sponsored by: Splunk Inc. Do you grep=20 > through log=20 > >files for problems? Stop! Download the new AJAX search engine that=20 > >makes searching your log files as easy as surfing the web. =20 > DOWNLOAD SPLUNK! > >http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D230486 > &dat=3D12164 > >2 _______________________________________________ > >Quickfix-users mailing list > >Qui...@li... > >https://lists.sourceforge.net/lists/listinfo/quickfix-users > > > > > > =20 > > >=20 >=20 > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep=20 > through log files for problems? Stop! Download the new AJAX=20 > search engine that makes searching your log files as easy as=20 > surfing the web. DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D230486& > dat=3D121642 > _______________________________________________ > Quickfix-users mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfix-users >=20 |
From: Chris v. O. <chr...@gn...> - 2006-02-17 11:24:31
|
> Hi Chris, > > Is the ResetOnLogout session option what you want? You > would logout using your local Session object which would > send a logout message to the other process. The logout would > cause a reset of the message store (resend log and sequence > numbers) in the remote session if the option above is enabled > in it's settings. This would mean you can't logout the session > /without/ starting a new logical session. Is that a problem > in your case? Steve, Thanks for the reply. This is handy information, but a little less than a perfect solution for me. I was hoping to be able to trigger an EOD from an option on my client app as I am doing alot of testing with re-sequencing against an acceptor type app and only need to EOD about half of the time. Maybe setting the option to true and killing my app uncleanly when I don't want to EOD will be a good workaround for me. Thanks for your help, Chris |
From: Oren M. <or...@qu...> - 2006-02-17 14:03:11
|
Steve, Does QuickFIX/J support the ResetSeqNum field? --oren Chris van Ophuijsen wrote: >QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html >QuickFIX Support: http://www.quickfixengine.org/services.html > > > >>Hi Chris, >> >>Is the ResetOnLogout session option what you want? You >>would logout using your local Session object which would >>send a logout message to the other process. The logout would >>cause a reset of the message store (resend log and sequence >>numbers) in the remote session if the option above is enabled >>in it's settings. This would mean you can't logout the session >>/without/ starting a new logical session. Is that a problem >>in your case? >> >> > > > Steve, > > Thanks for the reply. This is handy information, but a little less >than a perfect solution for me. I was hoping to be able to trigger an >EOD from an option on my client app as I am doing alot of testing with >re-sequencing against an acceptor type app and only need to EOD about >half of the time. Maybe setting the option to true and killing my app >uncleanly when I don't want to EOD will be a good workaround for me. > >Thanks for your help, >Chris > > > > > >------------------------------------------------------- >This SF.net email is sponsored by: Splunk Inc. Do you grep through log files >for problems? Stop! Download the new AJAX search engine that makes >searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! >http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 >_______________________________________________ >Quickfix-users mailing list >Qui...@li... >https://lists.sourceforge.net/lists/listinfo/quickfix-users > > > > |
From: Dale W. <wil...@oc...> - 2006-02-17 15:29:29
|
Hi Chris, Chris van Ophuijsen wrote: ><SNIP> >I was hoping to be able to trigger an >EOD from an option on my client app as I am doing alot of testing with >re-sequencing against an acceptor type app and only need to EOD about >half of the time. > The answer to your question depends on what you are trying to do. If you are stopping and restarting the application the cleanest solution may be to "manually" reset the sequence number files in the store directory -- probably in a script file you use to start the app. Another approach would be to put code in the onCreate callback to conditionally reset the expected sequence number(s) in the newly created Session before you actually start the initiator or acceptor. You probably don't want this code to escape into the production version. If you're trying to do this while keeping the applicaiton up and running then it's a more difficult proposition. If this is the case, provide more information about what you would like to happen (and maybe why (grin)) Dale >Maybe setting the option to true and killing my app >uncleanly when I don't want to EOD will be a good workaround for me. > >Thanks for your help, >Chris > > > > > >------------------------------------------------------- >This SF.net email is sponsored by: Splunk Inc. Do you grep through log files >for problems? Stop! Download the new AJAX search engine that makes >searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! >http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 >_______________________________________________ >Quickfix-users mailing list >Qui...@li... >https://lists.sourceforge.net/lists/listinfo/quickfix-users > > -- ----------------------------------------------------- Dale Wilson, Senior Software Engineer Object Computing, Inc. (OCI) http://www.ociweb.com/ http://www.theaceorb.com/ ---------------------------------------------------- |
From: Chris v. O. <chr...@gn...> - 2006-02-18 01:41:20
|
On Fri, 2006-02-17 at 09:29 -0600, Dale Wilson wrote: > The answer to your question depends on what you are trying to do. In a nutshell, I have a swing app (a highly altered Banzai) that I use to test our in-house, proprietary FIX handlers. This is just a tool I am using that I need to be able to quickly create and execute test scenarios. The developer is generally debugging the legacy code in Eclipse, and Im running also out of Eclipse.... it is frequent that we need to quickly come up with a "clean" session after he makes a code change. Currently, depending on if the session is so borked that we need to EOD, I have to quit my app, find the store directory in Eclipse, ask Eclipse to "refresh", then delete the store and seq numbers, then restart my app. It would be convenient if I could prompt a disconnect, then have an option to EOD from my GUI, then restart. Im sure I could parse the store location from the application config file and clobber the files myself, but I just figured that there was a method already in place to do that. It sounds like there isnt, or Im just not being clear enough about what Im trying to do. > If you are stopping and restarting the application the cleanest solution > may be to "manually" reset the sequence number files in the store > directory -- probably in a script file you use to start the app. Unfortunately there are too many variables to do it this way, and it still wouldnt be *as* convenient. > Another approach would be to put code in the onCreate callback to > conditionally reset the expected sequence number(s) in the newly created > Session before you actually start the initiator or acceptor. How would I do this? And would simply resetting the sequence numbers have the desired effect of ignoring any previous data in the message store? > You > probably don't want this code to escape into the production version. Luckily for mankind, it wont.... this is just a tool completely separate from any production code. > If you're trying to do this while keeping the applicaiton up and running > then it's a more difficult proposition. If this is the case, provide > more information about what you would like to happen (and maybe why (grin)) Its merely a convenience for me ... but I just imagined that there would be a method for this for the sake of developers and systems guys. Thanks for your help, Chris |