|
From: Colin D. <co...@ma...> - 2018-01-26 15:47:31
|
I don't think it's possible to distinguish between "actually sent" and "queued" except indirectly. In both cases, sendMessage will return true. In the case of "actually sent", you should get some kind of reply back from the counter. For example, a new order should return an ER of Pending New status, though this is optional and not all counters will do it. What we do is set a timer and track whether we got some kind of response for an outgoing message. It's not completely deterministic, but it can at least give you a hint. On 01/26/2018 07:26 AM, Bartłomiej Kruczyk wrote: > QuickFIX/J Documentation: http://www.quickfixj.org/documentation/ > QuickFIX/J Support: http://www.quickfixj.org/support/ > > > > > Thanks for response! > > I have a problem with this approach though, how can I check if message > has been actually sent or that it is queued? > > PS. I think this issue should be stated more clearly in quickfix/j > javadoc. > > z poważaniem > Bartłomiej Kruczyk > > 2018-01-26 15:23 GMT+01:00 Christoph John <chr...@ma... > <mailto:chr...@ma...>>: > > Hi, > > this cannot be done in QFJ itself. Unless you never reset the > sequence numbers automatically. > > Usually this can be achieved by having a sequencing in your stored > data as well. When you send out messages you store the sent > internal sequence "number" (e.g. date plus increasing number). > When the session comes up the next time, you subscribe only the > data that has a higher sequence number than the one that you > already sent out. > > A more brute-force approach could be to have your application > check if there are still messages in the store, waiting to be > sent. If yes, store these messages (memory or disk), reset the > sequence numbers and re-insert these messages into the store. > > I'm sure there are also other ways to tackle this. > > Regards, > Chris. > > > On 26/01/18 14:47, Bartłomiej Kruczyk wrote: >> QuickFIX/J Documentation:http://www.quickfixj.org/documentation/ >> <http://www.quickfixj.org/documentation/> >> QuickFIX/J Support:http://www.quickfixj.org/support/ <http://www.quickfixj.org/support/> >> >> >> >> >> Hello! >> >> I know that quickfix is queueing messages in message store and >> sends them when other party is logged into the session. My >> problem is that when new session starts, the sequence number is >> resetted to 1 and thus messages queued after session end time >> (but before star time) are never being sent to counterparty. Is >> there a way for a quickfix to ensure that the message will always >> been sent, preferably at the begging of the new session? >> >> Best regards >> Bartłomiej Kruczyk >> >> >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org!http://sdm.link/slashdot >> >> >> _______________________________________________ >> Quickfixj-users mailing list >> Qui...@li... >> <mailto:Qui...@li...> >> https://lists.sourceforge.net/lists/listinfo/quickfixj-users >> <https://lists.sourceforge.net/lists/listinfo/quickfixj-users> > > -- > Christoph John > Development & Support > T+49 241 557080-28 <tel:+49%20241%2055708028> > chr...@ma... <mailto:chr...@ma...> > > MACD GmbH > Oppenhoffallee 103 > D-52066 Aachen > www.macd.com <http://www.macd.com> > > Amtsgericht Aachen: HRB 8151 > Ust.-Id: DE813021663 <tel:81%20302%2016%2063> > Geschäftsführer: George Macdonald > > > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > > _______________________________________________ > Quickfixj-users mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfixj-users -- Colin DuPlantis Chief Architect, Marketcetera Download, Run, Trade 888.868.4884 +1.541.306.6556 http://www.marketcetera.org |