Skip to content
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

ValidateFieldsOutOfOrder=N not working #709

Open
obiben opened this issue Nov 5, 2021 · 1 comment
Open

ValidateFieldsOutOfOrder=N not working #709

obiben opened this issue Nov 5, 2021 · 1 comment

Comments

@obiben
Copy link

obiben commented Nov 5, 2021

I'm connecting to a broker that sends my TargetSubID as the second to last field in their ExecutionReport messages, and that causes QuickFix to reply with a Reject message.

ValidateFieldsOutOfOrder=N

in my config or

        SessionSettings settings = new SessionSettings("config.cfg");
	Dictionary defaults = settings.Get();
	defaults.SetBool(SessionSettings.VALIDATE_FIELDS_OUT_OF_ORDER, false);
	settings.Set(defaults);
        IMessageStoreFactory storeFactory = new FileStoreFactory(settings);
        ILogFactory logFactory = new FileLogFactory(settings);

        this.application = new Quickfix.Application();
        this.initiator = new QuickFix.Transport.SocketInitiator(application, storeFactory, settings, logFactory);

for good measure seem to have no effect, the execution report still gets rejected.

@obiben
Copy link
Author

obiben commented Nov 5, 2021

After a good bit of reading the source, I found the workaround to be

Session.LookupSession(sessionId).SessionDataDictionary.CheckFieldsOutOfOrder = false;

in Application.OnCreate. It seems the configuration isn't properly applied to DataDictionnaries.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant