{{Quickfixn}} Sending Time Accuracy

[Ruaan Viljoen]

I noticed a FIXME for CheckLatency in Quickfix.SessionFactory. Finishing (what I think was) the implementation and recompiling solved the Sending Time accuracy problem, but if I would like to contribute a pull request I would need to add some unit tests etc.? Perhaps someone could provide me with a hint as to what is required to contribute I would be glad to go the whole mile and help the project.

Regards
Ruaan

From: quickfixn-bounces at lists.quickfixn.com [mailto:quickfixn-bounces at lists.quickfixn.com] On Behalf Of Ruaan Viljoen
Sent: 10 September 2012 02:14 PM
To: Mailing list for QuickFIX/n (quickfixn at lists.quickfixn.com)
Subject: {{Quickfixn}} Sending Time Accuracy

I am having some trouble with the following, I can't seem to log on successfully to my counterparty it seems. I *think* our initiator is rejecting their logon response?
Event log:
20120910-11:45:38.994 : Sending time accuracy problem
20120910-11:45:38.994 : Message 1 Rejected: 10
20120910-11:45:38.994 : Verify failed: Tried to send a reject while not logged on
Etc.

I have seen mention of CheckLatency=N to ignore some time sync issues, but I found a post by Grant
stating that it is currently not implemented in Quickfix/n. I have not found any information to the contrary,
and after adding it to my .cfg file I still het the Sending Time accuracy problems.

Am I even barking up the right tree here, or should I be looking at other causes to solve this issue (or find a workaround)?

It worked fine until yesterday, could it be time sync issues with our server or our counterparty's?

Thanks
Ruaan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.quickfixn.com/pipermail/quickfixn-quickfixn.com/attachments/20120910/d965cd7b/attachment-0002.htm>