|
From: Steve B. <st...@te...> - 2007-03-21 15:25:21
|
> (I did not see any error printout in my log which means QFJ did not throw > any exception.) I guess it is something to do with the unique key > constrain on the message table which include sequence number. I had > to delete the rows in message table and restart and then everything > became ok. I understand tue design philosophy here is to try to be > more strict , but as a result it is less resilient in reality. > (QuickFIX does not have this issue). Alvin, from what I see in SVN, QuickFIX also includes the sequence number in the primary key. Can you explain how there would not have been a unique key voliation when using QuickFIX? > > Even stranger thing is I found the following SQL Server's error log. > |--------------------------------------------------------------------------| > | Conversion failed when converting the nvarchar value '8=FIX.4.49 > | > | =5835=534=249=FFTWFIX52=20070321-12:59:29.48756=TTTTTWEB10=089' to data > | type int. What is the messages column type in your MSSQL table? On the surface it appears you have an incorrect column type in your table. I suppose it's also possible that it's some MSSQL quirk, but that's less likely. |