|
From: Colin D. <co...@ma...> - 2023-05-17 13:10:13
|
Possibly. If the engine detects an inaccuracy, it will disconnect. You may miss messages, I would think, in that scenario. This situation must be corrected. Can you give an example of a message that was in the log but not received in fromApp? > On May 17, 2023, at 5:36 AM, Elyse Badr <ely...@ca...> wrote: > > Does the time inaccuracy cause Quickfix/J to receive the message from counter party but not transmitting it to the Java listener? > Example: the reply time of the market was before 2 seconds from the message time > The FIX messages are well present in the FIX logs but does not reach Java MessageCracker class. > I tried to use a thread to execute the messages as suggested in https://www.quickfixj.org/jira/browse/QFJ-875 > But still same issue. Please help. Should we contact the market? > > Thank you in advance for your support. > Elyse Badr > Senior Software Engineer > > Landline +961 5 428 300 > > <image001.png> > > WWW.CAPITAL-BANKING.COM <applewebdata://CCE5BD5E-701C-467F-921C-2DD07708FFE6/WWW.CAPITAL-BANKING.COM> > > From: Colin DuPlantis <co...@ma...> > Sent: Wednesday, May 17, 2023 3:17 PM > To: qui...@li... > Subject: Re: [Quickfixj-users] Production issue - Loss of messages + inaccurate time > > I would suggest that the system time is inaccurate on either your machine or that of your counter party's. > > On Wed, May 17, 2023, 3:47 AM Elyse Badr <ely...@ca... <mailto:ely...@ca...>> wrote: > QFJ Documentation: http://www.quickfixj.org/documentation/ > QFJ Support: http://www.quickfixj.org/support/ > > > Hi all, > > Can you please help to solve the following issue: > After running QuickfixJ for several months without issues, we suddenly are facing some problems: > TEST requests sent > Heartbeat message have inaccurate time: the one received from the market seems to be before the one we sent in the fix messages log (by 1 second) > Although the server time seems in sync with the market > Reproduced on both windows and unix > We faced send time inaccurate disconnection, but after adding CheckLatency=N, no more disconnection > The above issues are causing delays in the reception of Java Fix messages although they are correctly logged in the FIX messages logs > > Any suggestions? > > Thank you in advance > Elyse Badr > Senior Software Engineer > > Landline +961 5 428 300 > > > > WWW.CAPITAL-BANKING.COM <http://www.capital-banking.com/> > > _______________________________________________ > Quickfixj-users mailing list > Qui...@li... <mailto:Qui...@li...> > https://lists.sourceforge.net/lists/listinfo/quickfixj-users |