Menu
▾
▴
Re: [Quickfixj-users] error in event_log
|
From: Alvin W. <AW...@FF...> - 2007-03-27 16:32:58
|
HI, Steve,
Did you get chance to reproduce this scenario? thanks.
Alvin
Alvin Wang/FFTW
03/21/2007 11:38 To
AM qui...@li....n
et
cc
qui...@li....n
et,
qui...@li...
eforge.net
Subject
Re: [Maybe Content Spam] Re:
[Quickfixj-users] error in
event_log(Document link: Alvin
Wang)
Hi Steve,
I see. Because I was using a old version of QF (quickfix-1.9.4?), it has
different table schema from the current version of QF.
I used the downloaded SQL scripts to create the tables, and it is working
properly when everything is normal. I used SQL server tool to re-create the
schema:
CREATE TABLE [dbo].[messages](
[beginstring] [char](8) COLLATE Latin1_General_BIN NOT NULL,
[sendercompid] [varchar](64) COLLATE Latin1_General_BIN NOT NULL,
[targetcompid] [varchar](64) COLLATE Latin1_General_BIN NOT NULL,
[session_qualifier] [varchar](64) COLLATE Latin1_General_BIN NOT
NULL,
[msgseqnum] [int] NOT NULL,
[message] [text] COLLATE Latin1_General_BIN NOT NULL,
PRIMARY KEY CLUSTERED
(
[beginstring] ASC,
[sendercompid] ASC,
[targetcompid] ASC,
[session_qualifier] ASC,
[msgseqnum] ASC
)WITH (IGNORE_DUP_KEY = OFF) ON [PRIMARY]
) ON [PRIMARY] TEXTIMAGE_ON [PRIMARY]
Could you try the same thing I did (even without using MSSever)?
Many thanks!
"Steve Bate"
<steve@technoetic
.com> To
Sent by: qui...@li....n
quickfixj-users-b et
ou...@li... cc
ceforge.net
Subject
[Maybe Content Spam] Re:
03/21/2007 11:25 [Quickfixj-users] error in
AM event_log
Please respond to
quickfixj-users@l
ists.sourceforge.
net
QuickFIX/J Documentation: http://www.quickfixj.org/documentation/
QuickFIX/J Support: http://www.quickfixj.org/support/
> (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.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Quickfixj-users mailing list
Qui...@li...
https://lists.sourceforge.net/lists/listinfo/quickfixj-users
*******************************************************************************
This e-mail message is intended solely for the use of the addressee.
The message may contain information that is privileged and
confidential.
Disclosure to anyone other than the intended recipient is prohibited.
If you are not the intended recipient, please do not disseminate,
distribute or copy this communication, by e-mail or otherwise. Instead,
please notify us immediately by return e-mail(including the original
message with your reply) and then delete and discard all copies of the
message. We have taken precautions to minimize the risk of transmitting
software viruses but nevertheless advise you to carry out your own
virus checks on any attachment to this message. We accept
no liability for any loss or damage caused by software viruses.
*******************************************************************************
|
