MySql Log - sender and target comp ids wrong for incoming messages

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

MySql Log - sender and target comp ids wrong for incoming messages

Dermot
QuickFIX Documentation: 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
_______________________________________________
Quickfix-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/quickfix-developers

log.JPG (122K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: MySql Log - sender and target comp ids wrong for incoming messages

Grant Birchmeier
QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/


I'm not sure what you are asking.  There's nothing wrong with your log.


On Mon, Nov 7, 2016 at 9:33 AM, <[hidden email]> wrote:
QuickFIX Documentation: 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
_______________________________________________
Quickfix-developers mailing list
[hidden email]
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.

------------------------------------------------------------------------------
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
_______________________________________________
Quickfix-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/quickfix-developers
Reply | Threaded
Open this post in threaded view
|

Re: MySql Log - sender and target comp ids wrong for incoming messages

Dermot
QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/


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, < [hidden email] > Wrote:
Documentation QuickFIX: 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
______________________________ _________________
Quickfix-Developers Mailing List [hidden email]https: //Lists.Sourceforge. net / lists / listinfo / quickfix- developers
[hidden email]




-
Grant Birchmeier
Connamara Systems, LLC
Made-To-Measure Trading Solutions.
Exactly what you need. No more. No less.



------------------------------------------------------------------------------
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
_______________________________________________
Quickfix-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/quickfix-developers

log.JPG (122K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: MySql Log - sender and target comp ids wrong for incoming messages

Grant Birchmeier
QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/


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, <[hidden email]> 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, < [hidden email] > Wrote:
Documentation QuickFIX: 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
______________________________ _________________
Quickfix-Developers Mailing List [hidden email]https: //Lists.Sourceforge. net / lists / listinfo / quickfix- developers
[hidden email]




-
Grant Birchmeier
Connamara Systems, LLC
Made-To-Measure Trading Solutions.
Exactly what you need. No more. No less.





--
Grant Birchmeier
Connamara Systems, LLC
Made-To-Measure Trading Solutions.
Exactly what you need. No more. No less.

------------------------------------------------------------------------------
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
_______________________________________________
Quickfix-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/quickfix-developers
Reply | Threaded
Open this post in threaded view
|

Re: MySql Log - sender and target comp ids wrong for incoming messages

Dermot
QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/


Yes understood. You're a hardcore FIX guy haha. I'm new to this.

Agreed - the FIX messages are fine. The columns got me confused. I wonder if that is a bug or intentional(?).

----- Original Message -----
From: Grant Birchmeier <[hidden email]>
To: [hidden email]
Cc: "[hidden email]" <[hidden email]>
Date: 2016/11/8, Tue 12:21
Subject: Re: [Quickfix-developers] MySql Log - sender and target comp ids wrong for incoming messages

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, <[hidden email]> 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, < [hidden email] > Wrote:
Documentation QuickFIX: 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
______________________________ _________________
Quickfix-Developers Mailing List [hidden email]https: //Lists.Sourceforge. net / lists / listinfo / quickfix- developers
[hidden email]




-
Grant Birchmeier
Connamara Systems, LLC
Made-To-Measure Trading Solutions.
Exactly what you need. No more. No less.





--
Grant Birchmeier
Connamara Systems, LLC
Made-To-Measure Trading Solutions.
Exactly what you need. No more. No less.



------------------------------------------------------------------------------
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
_______________________________________________
Quickfix-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/quickfix-developers
Reply | Threaded
Open this post in threaded view
|

Re: MySql Log - sender and target comp ids wrong for incoming messages

Mike Gatny
QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/


The other columns are correct -- they are a representation of the SessionID.  They do not change based on the content of a particular message. If you are familiar with the way the FileLog names its log files, this is the exact same concept.

--
Mike Gatny
Connamara Systems, LLC

On Mon, Nov 7, 2016 at 10:28 PM, <[hidden email]> wrote:
QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/


Yes understood. You're a hardcore FIX guy haha. I'm new to this.

Agreed - the FIX messages are fine. The columns got me confused. I wonder if that is a bug or intentional(?).

----- Original Message -----
From: Grant Birchmeier <[hidden email]>
To: [hidden email]
Cc: "[hidden email]" <[hidden email]>
Date: 2016/11/8, Tue 12:21
Subject: Re: [Quickfix-developers] MySql Log - sender and target comp ids wrong for incoming messages

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, <[hidden email]> 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, < [hidden email] > Wrote:
Documentation QuickFIX: 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
______________________________ _________________
Quickfix-Developers Mailing List [hidden email]https: //Lists.Sourceforge. net / lists / listinfo / quickfix- developers
[hidden email]




-
Grant Birchmeier
Connamara Systems, LLC
Made-To-Measure Trading Solutions.
Exactly what you need. No more. No less.





--
Grant Birchmeier
Connamara Systems, LLC
Made-To-Measure Trading Solutions.
Exactly what you need. No more. No less.



------------------------------------------------------------------------------
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
_______________________________________________
Quickfix-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/quickfix-developers


------------------------------------------------------------------------------
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
_______________________________________________
Quickfix-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/quickfix-developers
Reply | Threaded
Open this post in threaded view
|

Re: MySql Log - sender and target comp ids wrong for incoming messages

Grant Birchmeier
QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/


Ah, of course, the session id.  Duh on me.

On Tue, Nov 8, 2016 at 9:55 AM, Mike Gatny <[hidden email]> wrote:
The other columns are correct -- they are a representation of the SessionID.  They do not change based on the content of a particular message. If you are familiar with the way the FileLog names its log files, this is the exact same concept.

--
Mike Gatny
Connamara Systems, LLC

On Mon, Nov 7, 2016 at 10:28 PM, <[hidden email]> wrote:
QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/


Yes understood. You're a hardcore FIX guy haha. I'm new to this.

Agreed - the FIX messages are fine. The columns got me confused. I wonder if that is a bug or intentional(?).

----- Original Message -----
From: Grant Birchmeier <[hidden email]>
To: [hidden email]
Cc: "[hidden email]" <[hidden email]>
Date: 2016/11/8, Tue 12:21
Subject: Re: [Quickfix-developers] MySql Log - sender and target comp ids wrong for incoming messages

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, <[hidden email]> 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, < [hidden email] > Wrote:
Documentation QuickFIX: 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
______________________________ _________________
Quickfix-Developers Mailing List [hidden email]https: //Lists.Sourceforge. net / lists / listinfo / quickfix- developers
[hidden email]




-
Grant Birchmeier
Connamara Systems, LLC
Made-To-Measure Trading Solutions.
Exactly what you need. No more. No less.





--
Grant Birchmeier
Connamara Systems, LLC
Made-To-Measure Trading Solutions.
Exactly what you need. No more. No less.



------------------------------------------------------------------------------
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
_______________________________________________
Quickfix-developers mailing list
[hidden email]
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.

------------------------------------------------------------------------------
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
_______________________________________________
Quickfix-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/quickfix-developers
Reply | Threaded
Open this post in threaded view
|

Re: MySql Log - sender and target comp ids wrong for incoming messages

Dermot
In reply to this post by Mike Gatny
QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/


Thanks Mike. Understood.

----- Original Message -----
From: Mike Gatny <[hidden email]>
To: [hidden email]
Cc: Grant Birchmeier <[hidden email]>; "[hidden email]" <[hidden email]>
Date: 2016/11/9, Wed 00:55
Subject: Re: [Quickfix-developers] MySql Log - sender and target comp ids wrong for incoming messages

The other columns are correct -- they are a representation of the SessionID.  They do not change based on the content of a particular message. If you are familiar with the way the FileLog names its log files, this is the exact same concept.

--
Mike Gatny
Connamara Systems, LLC

On Mon, Nov 7, 2016 at 10:28 PM, <[hidden email]> wrote:
QuickFIX Documentation: http://www.quickfixengine.org/ quickfix/doc/html/


Yes understood. You're a hardcore FIX guy haha. I'm new to this.

Agreed - the FIX messages are fine. The columns got me confused. I wonder if that is a bug or intentional(?).

----- Original Message -----
From: Grant Birchmeier <[hidden email]>
To: [hidden email]
Cc: "[hidden email]" <[hidden email]>
Date: 2016/11/8, Tue 12:21
Subject: Re: [Quickfix-developers] MySql Log - sender and target comp ids wrong for incoming messages

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, <[hidden email]> 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, < [hidden email] > Wrote:
Documentation QuickFIX: 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
______________________________ _________________
Quickfix-Developers Mailing List [hidden email]https: //Lists.Sourceforge. net / lists / listinfo / quickfix- developers
[hidden email]




-
Grant Birchmeier
Connamara Systems, LLC
Made-To-Measure Trading Solutions.
Exactly what you need. No more. No less.





--
Grant Birchmeier
Connamara Systems, LLC
Made-To-Measure Trading Solutions.
Exactly what you need. No more. No less.



------------------------------ ------------------------------ ------------------
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
______________________________ _________________
Quickfix-developers mailing list
[hidden email]
https://lists.sourceforge.net/ lists/listinfo/quickfix- developers




------------------------------------------------------------------------------
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
_______________________________________________
Quickfix-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/quickfix-developers