[QFJ-441] Sending time accuracy problem Created: 05/Jun/09 Updated: 15/Apr/11 Resolved: 20/Mar/11 |
|
| Status: | Closed |
| Project: | QuickFIX/J |
| Component/s: | None |
| Affects Version/s: | 1.4.0 |
| Fix Version/s: | None |
| Type: | Other | Priority: | Critical |
| Reporter: | Md Sarfaraz Asad Khan | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Linux |
||
| Description |
|
when ever we are hitting fix gateway we are trying to capture all trades till that time. that means : if i hit gateway at 9:30 - i fetch all trades till 9:30 (100 let) if i hit gateway at 10:30 - i fetch all trades till 10:30 (100 of 9:30+100 trads between 9:30 to 10:30 let) and so on till 2:30 when trade volume increases 6500 then the following error occoures : " SendingTime accuracy problem " NOTE :- clock is synchronized and NTP is working fine on both the server . |
| Comments |
| Comment by Tausseef Ahmad [ 07/Jul/10 ] |
|
CheckLatency=N put this tag in .cfg file |
| Comment by Steve Bate [ 15/Apr/11 ] |
|
During message resend, if a received resent message has an original sending time greater than the resent message sending time then this will cause the session to be terminated. This indicates some type of logical error in the server during the resend process. In other words, this situation says the message was resent before it was sent, which doesn't make sense. The CheckLatency flag does not turn off this check. The flag is for time skew on the normal message stream. |