Re: [Quickfix-developers] MySql Log - sender and target comp ids wrong for incoming messages
Brought to you by:
orenmnero
From: Grant B. <gbi...@co...> - 2016-11-08 03:21:37
|
Oh, I see -- you're looking at the sendercompid/targetcompid columns in your DB table. I didn't even look at those; because I instinctively ignore anything that is not raw FIX. My eyes went directly to the raw messages in the column on the right. (Always look at raw FIX messaging first!) In that raw message column, you can see that tags 49 and 56 are set exactly as they ought to be. The DB logging implementation appears to be setting the sender/target compid columns to match the client that is being logged, no matter whether the message is going in or out. (I've never used the DB logger myself.) On Mon, Nov 7, 2016 at 6:13 PM, <daw...@ya...> wrote: > Hi Grant, Thanks for your response. Maybe I misunderstood how this should > work. The logging here is enabled on the client app but it's capturing > messages going both ways. So looking at the attached pic the first entry in > the messages_log table entry is the client login request to the executor:- > > id: 1 > sendercompid: CLIENT_A > targetcompid: EXECUTOR > text: > 8=FIX.4.49=8235=A34=149=CLIENT_A52=20161107-14:31:50. > 87256=EXECUTOR98=0108=6000554=pass10=197 > > That's what I would expect to see. Then the 2nd entry is the response from > the executor. > > id: 2 > sendercompid: CLIENT_A > targetcompid: EXECUTOR > text: > 8=FIX.4.49=7335=A34=149=EXECUTOR52=20161107-14:31:50. > 91356=CLIENT_A98=0108=600010=046 > In this case shouldn't the sendercompid field show 'EXECUTOR' and the > targetcompid field show 'CLIENT_A' as per the fix message? Or because the > logging is enabled on the client side sendercompid will always be CLIENT_A > and targetcompid will always be EXECUTOR? > > Thanks, > Dermot > > Original Message ----- ----- *From:* Grant Birchmeier > <Gbirchmeierattoconnamara.Com> *To:* Dawntrader001attoyahoo.Co.Jp *Cc:* " > Quickfix-developersattolists.Sourceforge.Net" <Quickfix-Developers Atto > Lists.Sourceforge.Net> *Date:* 2016/11/8, Tue 06:44 *Subject:* Re: > [Quickfix-Developers] MySql Log - Sender And Target Comp Ids Wrong For > Incoming Messages > > > > > > > I'm not sure what you are asking. There's nothing wrong with your log. > > > Mon On, Nov 7, 2016 At 9:33 AM AM, < Dawntrader001attoyahoo.Co.Jp > <daw...@ya...> > Wrote: > > Documentation QuickFIX: Http://Www.Quickfixengine.Org/ Quickfix / doc / > Html / <http://www.quickfixengine.org/quickfix/doc/html/> > > > Pic attached this time ... > > > Hi Guys, I Just Enabled MySql Logs And Tested With A Simple Log In And Log > Out (Please See The Pic In Link). For Incoming Messages The Sendercompid > Shows The Client App And The Targetcompid Shows The Executor App So > Basically Sender And Target Are The same for all messages. Any Ideas? > Thanks, > Dermot > > ------------------------------ -------------------- ------------------ > ---------- > Developer Access Program For Intel Xeon Phi Processors > Access To Intel Xeon Phi Processor-Based Developer Platforms. > With One Year . Of Intel Parallel Studio XE > . Training And Support From Colfax > . Order Your Platform Today Http://Sdm.Link/xeonphi > <http://sdm.link/xeonphi> > ______________________________ _________________ > Quickfix-Developers Mailing List Quickfix-Developers Atto Lists > sourceforge.net. <Qui...@li...>https: > //Lists.Sourceforge. net / lists / listinfo / quickfix- developers > <https://lists.sourceforge.net/lists/listinfo/quickfix-developers> > <Qui...@li...> > <https://lists.sourceforge.net/lists/listinfo/quickfix-developers> > > > > > - > Grant Birchmeier > *Connamara Systems, LLC* > *Made-To-Measure Trading Solutions.* > Exactly what you need. No more. No less. > http://connamara.com > > > -- Grant Birchmeier *Connamara Systems, LLC* *Made-To-Measure Trading Solutions.* Exactly what you need. No more. No less. http://connamara.com |