-
Notifications
You must be signed in to change notification settings - Fork 560
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incorrect BeginString (FIX.4.4) in c# (Quickfixn) on windows machine while receiving X MsgType #894
Comments
I'm sure it's not the linux issue from #663, but it might be #864, which will be in the next release. I'm trying to confirm that. I don't think the problem is about 35=X. In the log you just posted, it looks like it first triggers on the 35=W.
If you are concerned about posting anything publicly, you can email me privately. My email is easy to find. |
Are you able to try this? Any questions about my request? |
Hello, sorry for not responding I was on holiday this week,
|
QF users really need to understand that the FIX message logs generated by a LogFactory are the prime source of truth to what the engine is actually doing. Any other logging that you implement is secondary, and may actually be misleading. If you don't see messages in the FIX log, then they are probably not being sent! Please attach the event log and message log from that connection! |
Hi,
I'm working on managing a market data stream using the FIX Protocol with QuickFIXn (version 1.12.0) on a Windows machine, specifically using FIX 4.4. After successfully connecting to the server, I receive a market data message (MsgType X), but it results in the following error you can see below
This error only occurs when subscribing to market data, also before message X there always comes a response with MarketDataSnapshot(W). There are no indications of missing tags or any rejection messages that would trigger a logout or session termination.
It looks like similar issue from this PR #663 which was referring to linux machine. If necessary, I can provide more details with configuration.
Sender headers
Full logs for MD session from connection to session termination by system
The text was updated successfully, but these errors were encountered: