quickfix-users — QuickFIX user support

Re: [Quickfix-users] [Quickfix-developers] Quickfix for FIX 5.0.....

[Nick E. <ni...@de...>]

Hi,

Thank you for such emotional answer I'll try to reply not to the =
emotions but facts
    1. quickfix does implicit transaction management passing fix =
messages one-by-one (transaction completed if client didn't trhow an =
exception). obviously while serving the message I have to perform =
tranaction in the database. hence we have obvious (just for me?) =
limitation on messages per second throughput. Hey, ma! where is the =
batches??? Even jms api has nice contract -- message.confirm(); =
confirming all the previous messages received so far.


  Wrong. Wrong. Wrong.  Not even wrong. You have somehow come under the =
impression that QuickFIX is a message queuing product.  Let me be the =
first to dissuade you of that notion.  You want a transactional message =
queue?  Then stick the message in a transactional message queue.  There =
are lots of products out there that do that, QuickFIX isn't one of them. =
Users who build high performance systems do not want the added over head =
of a transactional message queue just because you can't figure out how =
to piece the two together.  Believe it or not, some who write high =
frequency trading systems have figured out how to do so without a =
message queue or a database.  I'll leave you to figure out how.
You're missing the whole point. I'm not talking about storing messages =
in the database I'm talking about business transactions. They are about =
to happen somethere either in sync or async way, right? Hence the point =
was that quickfix doesn't make things easier in this way, because I have =
to use another abstraction to do batching. Please read it literally -- =
"I want to do batch insert at the end of the chain to insert 1000 orders =
in database at once". The only working solution with quickfix is to =
route it's messages somethere to perform async processing. Hence to use =
it not like queue but rather like transport adapter... You also pointed =
this out but in very inpolite manner. Such infrastructure involves a =
couple of rmi calls which also slows things down. It's always a good =
position to tell -- hey you're an idiot we've provided you a tool that =
is just a trasport! don't expect more. But may I ask you a question? Is =
architecture I'm describing would be harder to implement? Would it =
result bigger code? (I would not say for c++ but in java the code will =
be even simpler:)) As result you will have much more flexible product.

  Organizations like Reuters, CME, Pipeline, optionsXpress and many =
others have built massive systems with QuickFIX which run hundreds of =
simultaneous sessions processing hundreds or thousands of messages per =
second.  The fact that you can't only speaks to your incompetence.  =
Please. Leave QuickFIX out of it.
100 * 100 * 1000 =3D=3D 10 000 000 optionsXpress is able to process 10 =
millions orders per second? don't make my shoes laugh :)

Jumping on person is your style right? Is it because of lacking =
arguments? Do you know how many boxes do they use to handle it? Do you =
know why? because if you use fixengine just as transport  you have to =
build/buy messaging infrastracture set several boxes to perform task =
that could be done just by one blade server... Sometimes you don't care =
about it sometimes you do.
    2. Broken push message model implementation: thread in native code =
holding the lock while propagating message to java. get deadlock prone =
code as a bonus right? It's easy to fix but much better to have pull =
message model.


  Broken is highly exaggerated and isn't born out in the field.  Since =
you say it's easy to fix it is surprising you bring this up as a major =
issue and even more surprising you've not submitted a patch.
It was not a top issue it's just an annoying implementation detail. And =
I'm not a c++ developer. just java. sorry. But basicly all you need is =
not to hold monitor while calling java code, but use lock idiom -- flag =
checking under the mutex.

    3. Never ending reset sequence fixes which are just never working =
right in all (valid) cases.


  Most of the reset scenarios have been fixed.  Almost nobody notices =
bugs here because almost nobody uses this functionality.  One person who =
did, you, didn't do anything to help the situation. Not all scenarios =
have been implemented because no one is really demanding them.  We went =
for years without any reset support and no one even noticed. =20
Everything is quite simple. Nobody warns me neither in documentation nor =
other way. Hey, dude! our reset sequence code is alpha qaulity use it on =
your own risk. It was kind of surprise to me.. and finally decison was =
made to get rid of quickfix because of the reason #1 not #3.
  I'll tell you what's going on here Nick.  You made some promises to =
deliver, you failed, and now QuickFIX is going to be the fall guy.  It =
took you 6 months to figure out that QuickFIX didn't meet your needs?  =
That's some evaluation, did someone pay for you to waste all that time?
Probably you do have god's number because you know things you're not =
supposed to know. would you send it to me? Yes I was paid because =
solution with qf was developed in about a month, most time of which were =
spent on integration issues. And it was working ok... But finally we =
decided to develop ourown implementation in pure java that is why I'm =
talking about six month...



  QuickFIX is designed to meet the needs of thousands of users.  It is =
designed to be portable, works with standard and broken implementation =
of the FIX protocol, integrates with any database, file storage, custom =
storage, custom and out of the box logging, has a web interface, =
documentation, tons of settings, is written in portable C++ that =
compiles under many compilers on many operating systems.  It builds =
right out of the box and also comes in pre-built binaries for windows.  =
It has APIs in C++, Java, .NET, Ruby and Python plus a full from scratch =
pure Java implementation. That's just for starters. It's been in =
production use for 5 years and has, let me just say, an astounding =
amount of production implementations by an even more astounding group of =
well respected financial companies.                                      =
                                              .
Probably this should be output to log on startup to prevent complains :)
  So you can write an implementation in a single platform that meets =
your specific needs designed to fit into your exact architecture.  Big =
deal hotshot.
java is supposed to work on many platforms :)... bigdeal?
  I'm sorry to hear that your leaving, but Don't worry about us Nick.  =
>From now on everyone on the list will look to what someone once posted =
on this very list as our guiding inspiration.


  "as for everything else -- just keep moving! quickfix rocks :)"
      -- Nick Evgeniev (May 31, 2005)
I don't reclaim my words :)... Keep moving! change it to be more high =
performant, as changes are not as expensive :))

Re: [Quickfix-users] Quickfix for FIX 5.0.....

[Nick E. <ni...@de...>]

Hi,

I'm neither selling nor advertising our engine, just stating the fact. =
If you think that my points aren't valid just tell me where I'm wrong. =
Probably commercial engines are much worse than quickfix just  don't =
know, haven't tried them.
I can just repeat mine:

1. quickfix does implicit transaction management passing fix messages =
one-by-one (transaction completed if client didn't trhow an exception). =
obviously while serving the message I have to perform tranaction in the =
database. hence we have obvious (just for me?) limitation on messages =
per second throughput. Hey, ma! where is the batches??? Even jms api has =
nice contract -- message.confirm(); confirming all the previous messages =
received so far.

2. Broken push message model implementation: thread in native code =
holding the lock while propagating message to java. get deadlock prone =
code as a bonus right? It's easy to fix but much better to have pull =
message model.

3. Never ending reset sequence fixes which are just never working right =
in all (valid) cases.

4. At least as of version 1.11.* native code crashes (or silent death of =
acceptor thread) on invalid messages in login phase.

5. Last but not the least -- very GC unfriendly. shure it's not the =
issue until you implement batches, or explicit transaction management.
  ----- Original Message -----=20
  From: Oren Miller=20
  To: Nick Evgeniev=20
  Cc: Eranga Samararathna ; qui...@li... ; =
qui...@li...=20
  Sent: Wednesday, October 25, 2006 7:05 PM
  Subject: Re: [Quickfix-users] Quickfix for FIX 5.0.....


  Great points Nick.  If anyone wants a real fix engine, contact =
ni...@de....


  --oren


  On Oct 25, 2006, at 9:37 AM, Nick Evgeniev wrote:


    QuickFIX Documentation: =
http://www.quickfixengine.org/quickfix/doc/html/index.html
    QuickFIX Support: http://www.quickfixengine.org/services.html


    Hi,

    don't know about fix 5.0
    quickfix obviously needs architecture changes in it's current state =
it suited well only for fix sandboxes, as it has no explicit transaction =
management, hence it has no batching operations. it has brokenly =
designed synchronization and as a bonus has numerous errors in reset =
sequence handling and unexpected crashes in native code in connection =
handling.
    The last two issues are implementation details, but the first two =
are crucial for high volume transaction processing.
    We'd been evaluating quickfix for about half year, but finally =
decided to drop it in favor of homegrown engine because of issues I've =
written above.
    Just wonder that nowadays, after all the litrechure regarding =
highspeed message parsing available for $30 bucks at amazon, we have =
such brokenly designed product :(

Re: [Quickfix-users] Quickfix for FIX 5.0.....

[Oren M. <or...@qu...>]

Great points Nick.  If anyone wants a real fix engine, contact  
ni...@de....

--oren

On Oct 25, 2006, at 9:37 AM, Nick Evgeniev wrote:

> QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/ 
> html/index.html
> QuickFIX Support: http://www.quickfixengine.org/services.html
>
> Hi,
>
> don't know about fix 5.0
> quickfix obviously needs architecture changes in it's current state  
> it suited well only for fix sandboxes, as it has no explicit  
> transaction management, hence it has no batching operations. it has  
> brokenly designed synchronization and as a bonus has numerous  
> errors in reset sequence handling and unexpected crashes in native  
> code in connection handling.
> The last two issues are implementation details, but the first two  
> are crucial for high volume transaction processing.
> We'd been evaluating quickfix for about half year, but finally  
> decided to drop it in favor of homegrown engine because of issues  
> I've written above.
> Just wonder that nowadays, after all the litrechure regarding  
> highspeed message parsing available for $30 bucks at amazon, we  
> have such brokenly designed product :(
>

Re: [Quickfix-users] Quickfix for FIX 5.0.....

[Nick E. <ni...@de...>]

Hi,

don't know about fix 5.0
quickfix obviously needs architecture changes in it's current state it =
suited well only for fix sandboxes, as it has no explicit transaction =
management, hence it has no batching operations. it has brokenly =
designed synchronization and as a bonus has numerous errors in reset =
sequence handling and unexpected crashes in native code in connection =
handling.
The last two issues are implementation details, but the first two are =
crucial for high volume transaction processing.
We'd been evaluating quickfix for about half year, but finally decided =
to drop it in favor of homegrown engine because of issues I've written =
above.
Just wonder that nowadays, after all the litrechure regarding highspeed =
message parsing available for $30 bucks at amazon, we have such brokenly =
designed product :(


  ----- Original Message -----=20
  From: Eranga Samararathna=20
  To: qui...@li... ; =
qui...@li...=20
  Sent: Wednesday, October 25, 2006 9:50 AM
  Subject: [Quickfix-users] Quickfix for FIX 5.0.....


  QuickFIX Documentation: =
http://www.quickfixengine.org/quickfix/doc/html/index.html
  QuickFIX Support: http://www.quickfixengine.org/services.html




-------------------------------------------------------------------------=
-----


  Hi,

  =20

  How is the quickfix / quickfixj preparation for FIX 5.0? Is quickfix =
need architecture change to address the new loosely coupled FIX =
application layer and FIX session layer?

  =20

  BR,

  =20

  Eranga



-------------------------------------------------------------------------=
-----


  =
-------------------------------------------------------------------------=

  Using Tomcat but need to do more? Need to support web services, =
security?
  Get stuff done quickly with pre-integrated technology to make your job =
easier
  Download IBM WebSphere Application Server v.1.0.1 based on Apache =
Geronimo
  =
http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat=3D=
121642


-------------------------------------------------------------------------=
-----


  _______________________________________________
  Quickfix-users mailing list
  Qui...@li...
  https://lists.sourceforge.net/lists/listinfo/quickfix-users

Re: [Quickfix-users] [Quickfix-developers] Quickfix for FIX 5.0.....

[Oren M. <or...@qu...>]

Well the first cut will be likely to use the Session Protocol as the  
first supported transport for application messages.  This can be  
implemented with relatively little change to the architecture as it  
is pretty similar to how the previous versions work already.  This  
will require supporting the new versioning constructs while  
maintaining backwards compatibility with the old ones.  There will  
probably have to be some changes to how data dictionaries work, since  
I guess we will need two of them.

The first release of QF with 5.0 support will probably only implement  
transporting application messages over the session protocol.  After  
that I suppose it will come down to the first viable use case of  
sending application messages over a different transport.

--oren

On Oct 25, 2006, at 12:50 AM, Eranga Samararathna wrote:

> QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/ 
> html/index.html
> QuickFIX Support: http://www.quickfixengine.org/services.html
>
> Hi,
>
> How is the quickfix / quickfixj preparation for FIX 5.0? Is  
> quickfix need architecture change to address the new loosely  
> coupled FIX application layer and FIX session layer?
>
> BR,
>
> Eranga
>

[Quickfix-users] Quickfix for FIX 5.0.....

[Eranga S. <pe...@ri...>]

Hi,

 

How is the quickfix / quickfixj preparation for FIX 5.0? Is quickfix need
architecture change to address the new loosely coupled FIX application layer
and FIX session layer?

 

BR,

 

Eranga

Re: [Quickfix-users] RES: Trouble compiling, linker errors

[<Gre...@Ca...>]

I've fixed my problem by downloading the source distribution and building 
it myself. For whatever reason, now everything works fine, no more 
exceptions or linker errors. I suspect a problem in the binary 
distribution.

Greg Chabala





Greg CHABALA/ICF
10/20/2006 08:52 AM

To
Oren Miller <or...@qu...>
cc
qui...@li...
Subject
Re: [Quickfix-users] RES:  Trouble compiling, linker errors





In the project properties, under C++, Code Generation, Enable C++ 
Exceptions is set to Yes (/EHsc). At your prompting I tried the Yes With 
SEH setting as well, but it does not catch the exception either, so I put 
it back to Yes.

Greg Chabala





Oren Miller <or...@qu...> 
10/19/2006 06:47 PM

To
Gre...@Ca...
cc
qui...@li...
Subject
Re: [Quickfix-users] RES:  Trouble compiling, linker errors






Are you sure you have C++ exception handling enabled in your project?

--oren

On Oct 19, 2006, at 4:21 PM, Gre...@Ca... wrote:

The project was already doing a catch:   catch ( std::exception & e ) 

but it wasn't catching anything. 

I've commented most everything out now. I'm left with this: 


#include "FixApp.h" 

#include "quickfix\SessionSettings.h" 

using namespace std; 

int main() 
{ 
  
  try 
  { 
    std::string file = "Trade_Entry_Sample.ini"; 
    
    FIX::SessionSettings settings( file ); 
    return 0; 
  } 
  catch ( ... ) 
  { 
      std::cerr << "There was an error\n"; 
      return 1; 
  } 
} 

It still won't catch the error. 
It looks to be happening in the settings call based on the stack. I've 
checked the spelling of the ini file and moved a copy into the Debug 
folder just to be safe. 

Greg Chabala



-- 
This communication may contain privileged and/or confidential information 
and is intended solely for the addressee.  No waiver of confidentiality or 
privilege is made by mistransmission.  If you are not the intended 
recipient, you are hereby notified that any unauthorized dissemination, 
distribution, reading, printing, copying and/or use of this communication 
is strictly prohibited. If you have received this communication in error, 
please delete this message and immediately notify the sender by return 
e-mail.  Calyon Financial Inc. makes no representation or warranty 
regarding the correctness of any information contained herein, or the 
appropriateness of any transaction for any person. Nothing herein shall be 
construed as a recommendation to buy or sell any financial instrument or 
security. This communication is for informational purposes only.  Unless 
expressly stated, opinions in this e-mail are those of the individual 
sender and not of the Calyon Financial Group. For further information 
about the Calyon Financial Group, please see our website at  
http://www.calyonfinancial.com 

-- 
This communication may contain privileged and/or confidential information 
and is intended solely for the addressee.  No waiver of confidentiality or 
privilege is made by mistransmission.  If you are not the intended 
recipient, you are hereby notified that any unauthorized dissemination, 
distribution, reading, printing, copying and/or use of this communication 
is strictly prohibited. If you have received this communication in error, 
please delete this message and immediately notify the sender by return 
e-mail.  Calyon Financial Inc. makes no representation or warranty 
regarding the correctness of any information contained herein, or the 
appropriateness of any transaction for any person. Nothing herein shall be 
construed as a recommendation to buy or sell any financial instrument or 
security. This communication is for informational purposes only.  Unless 
expressly stated, opinions in this e-mail are those of the individual 
sender and not of the Calyon Financial Group. For further information 
about the Calyon Financial Group, please see our website at 
http://www.calyonfinancial.com 

Re: [Quickfix-users] RES: Trouble compiling, linker errors

[<Gre...@Ca...>]

In the project properties, under C++, Code Generation, Enable C++ 
Exceptions is set to Yes (/EHsc). At your prompting I tried the Yes With 
SEH setting as well, but it does not catch the exception either, so I put 
it back to Yes.

Greg Chabala





Oren Miller <or...@qu...> 
10/19/2006 06:47 PM

To
Gre...@Ca...
cc
qui...@li...
Subject
Re: [Quickfix-users] RES:  Trouble compiling, linker errors






Are you sure you have C++ exception handling enabled in your project?

--oren

On Oct 19, 2006, at 4:21 PM, Gre...@Ca... wrote:

The project was already doing a catch:   catch ( std::exception & e ) 

but it wasn't catching anything. 

I've commented most everything out now. I'm left with this: 


#include "FixApp.h" 

#include "quickfix\SessionSettings.h" 

using namespace std; 

int main() 
{ 
  
  try 
  { 
    std::string file = "Trade_Entry_Sample.ini"; 
    
    FIX::SessionSettings settings( file ); 
    return 0; 
  } 
  catch ( ... ) 
  { 
      std::cerr << "There was an error\n"; 
      return 1; 
  } 
} 

It still won't catch the error. 
It looks to be happening in the settings call based on the stack. I've 
checked the spelling of the ini file and moved a copy into the Debug 
folder just to be safe. 

Greg Chabala



-- 
This communication may contain privileged and/or confidential information 
and is intended solely for the addressee.  No waiver of confidentiality or 
privilege is made by mistransmission.  If you are not the intended 
recipient, you are hereby notified that any unauthorized dissemination, 
distribution, reading, printing, copying and/or use of this communication 
is strictly prohibited. If you have received this communication in error, 
please delete this message and immediately notify the sender by return 
e-mail.  Calyon Financial Inc. makes no representation or warranty 
regarding the correctness of any information contained herein, or the 
appropriateness of any transaction for any person. Nothing herein shall be 
construed as a recommendation to buy or sell any financial instrument or 
security. This communication is for informational purposes only.  Unless 
expressly stated, opinions in this e-mail are those of the individual 
sender and not of the Calyon Financial Group. For further information 
about the Calyon Financial Group, please see our website at 
http://www.calyonfinancial.com 

Re: [Quickfix-users] RES: Trouble compiling, linker errors

[Oren M. <or...@qu...>]

Are you sure you have C++ exception handling enabled in your project?

--oren

On Oct 19, 2006, at 4:21 PM, Gre...@Ca... wrote:

> The project was already doing a catch:   catch ( std::exception & e )
>
> but it wasn't catching anything.
>
> I've commented most everything out now. I'm left with this:
>
>
> #include "FixApp.h"
>
> #include "quickfix\SessionSettings.h"
>
> using namespace std;
>
> int main()
> {
>
>   try
>   {
>     std::string file = "Trade_Entry_Sample.ini";
>
>     FIX::SessionSettings settings( file );
>     return 0;
>   }
>   catch ( ... )
>   {
>       std::cerr << "There was an error\n";
>       return 1;
>   }
> }
>
> It still won't catch the error.
> It looks to be happening in the settings call based on the stack.  
> I've checked the spelling of the ini file and moved a copy into the  
> Debug folder just to be safe.
>
> Greg Chabala
>

Re: [Quickfix-users] RES: Trouble compiling, linker errors

[<Gre...@Ca...>]

The project was already doing a catch:   catch ( std::exception & e )

but it wasn't catching anything.

I've commented most everything out now. I'm left with this:


#include "FixApp.h" 

#include "quickfix\SessionSettings.h"

using namespace std;

int main()
{
 
  try
  {
    std::string file = "Trade_Entry_Sample.ini";
 
    FIX::SessionSettings settings( file );
    return 0;
  }
  catch ( ... )
  {
      std::cerr << "There was an error\n";
      return 1;
  }
}

It still won't catch the error.
It looks to be happening in the settings call based on the stack. I've 
checked the spelling of the ini file and moved a copy into the Debug 
folder just to be safe.

Greg Chabala





Oren Miller <or...@qu...> 
Sent by: qui...@li...
10/19/2006 02:14 PM

To
Gre...@Ca...
cc
qui...@li...
Subject
Re: [Quickfix-users] RES:  Trouble compiling, linker errors





You should trap the ConfigError and print out the message.  QuickFIX is 
trying to tell you that their is an error with the configuration that 
prevents it from running.  Perhaps a file that can't be open, or a 
directory that cannot be created.  You will need to trap and print out the 
exception to find the exact reason.

--oren

On Oct 19, 2006, at 2:06 PM, Gre...@Ca... wrote:


Yes, that's correct. I confused myself and picked the non-DLL 
multithreaded runtime library. 

Unfortunately, while I can now compile, my code crashes with a memory 
error: 

     Unhandled exception at 0x7c812a5b in fix-test-connection.exe: 
Microsoft C++ exception: FIX::ConfigError at memory location 0x0012f610 

and it breaks at line 107 in the C:\Program Files\Microsoft Visual Studio 
8\VC\crt\src\xutility and trying to continue just leads to stack overflow 
errors 



-- 
This communication may contain privileged and/or confidential information 
and is intended solely for the addressee.  No waiver of confidentiality or 
privilege is made by mistransmission.  If you are not the intended 
recipient, you are hereby notified that any unauthorized dissemination, 
distribution, reading, printing, copying and/or use of this communication 
is strictly prohibited. If you have received this communication in error, 
please delete this message and immediately notify the sender by return 
e-mail.  Calyon Financial Inc. makes no representation or warranty 
regarding the correctness of any information contained herein, or the 
appropriateness of any transaction for any person. Nothing herein shall be 
construed as a recommendation to buy or sell any financial instrument or 
security. This communication is for informational purposes only.  Unless 
expressly stated, opinions in this e-mail are those of the individual 
sender and not of the Calyon Financial Group. For further information 
about the Calyon Financial Group, please see our website at 
http://www.calyonfinancial.com 

Re: [Quickfix-users] RES: Trouble compiling, linker errors

[Oren M. <or...@qu...>]

You should trap the ConfigError and print out the message.  QuickFIX  
is trying to tell you that their is an error with the configuration  
that prevents it from running.  Perhaps a file that can't be open, or  
a directory that cannot be created.  You will need to trap and print  
out the exception to find the exact reason.

--oren

On Oct 19, 2006, at 2:06 PM, Gre...@Ca... wrote:

>
> Yes, that's correct. I confused myself and picked the non-DLL  
> multithreaded runtime library.
>
> Unfortunately, while I can now compile, my code crashes with a  
> memory error:
>
>      Unhandled exception at 0x7c812a5b in fix-test-connection.exe:  
> Microsoft C++ exception: FIX::ConfigError at memory location  
> 0x0012f610
>
> and it breaks at line 107 in the C:\Program Files\Microsoft Visual  
> Studio 8\VC\crt\src\xutility and trying to continue just leads to  
> stack overflow errors

Re: [Quickfix-users] RES: Trouble compiling, linker errors

[<Gre...@Ca...>]

Yes, that's correct. I confused myself and picked the non-DLL 
multithreaded runtime library.

Unfortunately, while I can now compile, my code crashes with a memory 
error:

     Unhandled exception at 0x7c812a5b in fix-test-connection.exe: 
Microsoft C++ exception: FIX::ConfigError at memory location 0x0012f610

and it breaks at line 107 in the C:\Program Files\Microsoft Visual Studio 
8\VC\crt\src\xutility and trying to continue just leads to stack overflow 
errors

And there is this linker warning still:

1>LINK : warning LNK4098: defaultlib 'MSVCRT' conflicts with use of other 
libs; use /NODEFAULTLIB:library

I assume that the code should run fine, as it used to run correctly in the 
past.

If I do as the linker suggests and exclude the library I get more linker 
errors:

1>------ Rebuild All started: Project: fix-test-connection, Configuration: 
Debug Win32 ------
1>Deleting intermediate and output files for project 
'fix-test-connection', configuration 'Debug|Win32'
1>Compiling...
1>Trade_Entry_Sample.cpp
1>FixApp.cpp
1>Generating Code...
1>Compiling manifest to resources...
1>Linking...
1>quickfix.lib(HttpConnection.obj) : error LNK2001: unresolved external 
symbol __imp___invalid_parameter_noinfo
1>quickfix.lib(HttpMessage.obj) : error LNK2001: unresolved external 
symbol __imp___invalid_parameter_noinfo
1>quickfix.lib(Settings.obj) : error LNK2001: unresolved external symbol 
__imp___invalid_parameter_noinfo
1>quickfix.lib(MSXML_DOMDocument.obj) : error LNK2001: unresolved external 
symbol __imp___invalid_parameter_noinfo
1>quickfix.lib(Acceptor.obj) : error LNK2001: unresolved external symbol 
__imp___invalid_parameter_noinfo
1>quickfix.lib(SocketServer.obj) : error LNK2001: unresolved external 
symbol __imp___invalid_parameter_noinfo
1>quickfix.lib(SocketMonitor.obj) : error LNK2001: unresolved external 
symbol __imp___invalid_parameter_noinfo
1>quickfix.lib(SocketConnection.obj) : error LNK2001: unresolved external 
symbol __imp___invalid_parameter_noinfo
1>quickfix.lib(HttpServer.obj) : error LNK2001: unresolved external symbol 
__imp___invalid_parameter_noinfo
1>quickfix.lib(SessionFactory.obj) : error LNK2001: unresolved external 
symbol __imp___invalid_parameter_noinfo
1>quickfix.lib(Message.obj) : error LNK2001: unresolved external symbol 
__imp___invalid_parameter_noinfo
1>quickfix.lib(DataDictionary.obj) : error LNK2001: unresolved external 
symbol __imp___invalid_parameter_noinfo
1>quickfix.lib(Dictionary.obj) : error LNK2001: unresolved external symbol 
__imp___invalid_parameter_noinfo
1>quickfix.lib(MessageStore.obj) : error LNK2001: unresolved external 
symbol __imp___invalid_parameter_noinfo
1>quickfix.lib(SocketInitiator.obj) : error LNK2001: unresolved external 
symbol __imp___invalid_parameter_noinfo
1>quickfix.lib(Initiator.obj) : error LNK2001: unresolved external symbol 
__imp___invalid_parameter_noinfo
1>quickfix.lib(SessionSettings.obj) : error LNK2001: unresolved external 
symbol __imp___invalid_parameter_noinfo
1>quickfix.lib(Utility.obj) : error LNK2001: unresolved external symbol 
__imp___invalid_parameter_noinfo
1>quickfix.lib(FieldMap.obj) : error LNK2019: unresolved external symbol 
__imp___invalid_parameter_noinfo referenced in function "public: bool 
__thiscall std::_Tree<class std::_Tmap_traits<int,class 
FIX::FieldBase,struct FIX::message_order,class std::allocator<struct 
std::pair<int const ,class FIX::FieldBase> >,1> 
>::const_iterator::operator==(class std::_Tree<class 
std::_Tmap_traits<int,class FIX::FieldBase,struct FIX::message_order,class 
std::allocator<struct std::pair<int const ,class FIX::FieldBase> >,1> 
>::const_iterator const &)const " 
(??8const_iterator@?$_Tree@V?$_Tmap_traits@HVFieldBase@FIX@@Umessage_order@2@V?$allocator@U?$pair@$$CBHVFieldBase@FIX@@@std@@@std@@$00@std@@@std@@QBE_NABV012@@Z)
1>quickfix.lib(Session.obj) : error LNK2001: unresolved external symbol 
__imp___invalid_parameter_noinfo
1>quickfix.lib(FileLog.obj) : error LNK2001: unresolved external symbol 
__imp___invalid_parameter_noinfo
1>quickfix.lib(FileStore.obj) : error LNK2001: unresolved external symbol 
__imp___invalid_parameter_noinfo
1>C:\Documents and Settings\gchabala\My Documents\Visual Studio 
2005\Projects\fix-test-connection\Debug\fix-test-connection.exe : fatal 
error LNK1120: 1 unresolved externals
1>Build log was saved at "file://c:\Documents and Settings\gchabala\My 
Documents\Visual Studio 
2005\Projects\fix-test-connection\Debug\BuildLog.htm"
1>fix-test-connection - 23 error(s), 0 warning(s)
========== Rebuild All: 0 succeeded, 1 failed, 0 skipped ==========

which looks like one perticular symbol is missing.

Greg Chabala





"Djalma Rosa dos Santos Filho" <drs...@bm...> 
10/19/2006 01:09 PM

To
<Gre...@Ca...>, <qui...@li...>
cc
"Oren Miller" <or...@qu...>
Subject
RES: [Quickfix-users] Trouble compiling, linker errors






Suggestion: check if your application and the quickfix.lib are both
using the same run-time library.

Example: if quickfix.lib was built using /MTd then your application
cannot use /MT.

To check go to C/C++ | Code Generation | Use run-time library.

Djalma

-----Mensagem original-----
De: qui...@li...
[mailto:qui...@li...] Em nome de
Gre...@Ca...
Enviada em: quinta-feira, 19 de outubro de 2006 13:37
Para: qui...@li...
Cc: Oren Miller
Assunto: Re: [Quickfix-users] Trouble compiling, linker errors

QuickFIX Documentation:
http://www.quickfixengine.org/quickfix/doc/html/index.html
QuickFIX Support: http://www.quickfixengine.org/services.html


-- 
This communication may contain privileged and/or confidential information 
and is intended solely for the addressee.  No waiver of confidentiality or 
privilege is made by mistransmission.  If you are not the intended 
recipient, you are hereby notified that any unauthorized dissemination, 
distribution, reading, printing, copying and/or use of this communication 
is strictly prohibited. If you have received this communication in error, 
please delete this message and immediately notify the sender by return 
e-mail.  Calyon Financial Inc. makes no representation or warranty 
regarding the correctness of any information contained herein, or the 
appropriateness of any transaction for any person. Nothing herein shall be 
construed as a recommendation to buy or sell any financial instrument or 
security. This communication is for informational purposes only.  Unless 
expressly stated, opinions in this e-mail are those of the individual 
sender and not of the Calyon Financial Group. For further information 
about the Calyon Financial Group, please see our website at 
http://www.calyonfinancial.com 

Re: [Quickfix-users] Trouble compiling, linker errors

[<Gre...@Ca...>]

Here is my output:

1>------ Rebuild All started: Project: fix-test-connection, Configuration: 
Debug Win32 ------
1>Deleting intermediate and output files for project 
'fix-test-connection', configuration 'Debug|Win32'
1>Compiling...
1>Trade_Entry_Sample.cpp
1>FixApp.cpp
1>Generating Code...
1>Compiling manifest to resources...
1>Linking...
1>msvcprt.lib(MSVCP80.dll) : error LNK2005: "public: __thiscall 
std::basic_string<char,struct std::char_traits<char>,class 
std::allocator<char> >::basic_string<char,struct 
std::char_traits<char>,class std::allocator<char> >(class 
std::basic_string<char,struct std::char_traits<char>,class 
std::allocator<char> > const &)" 
(??0?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QAE@ABV01@@Z) 
already defined in FixApp.obj
1>msvcprt.lib(MSVCP80.dll) : error LNK2005: "public: __thiscall 
std::basic_string<char,struct std::char_traits<char>,class 
std::allocator<char> >::~basic_string<char,struct 
std::char_traits<char>,class std::allocator<char> >(void)" 
(??1?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QAE@XZ) 
already defined in FixApp.obj
1>msvcprt.lib(MSVCP80.dll) : error LNK2005: "class 
std::basic_string<char,struct std::char_traits<char>,class 
std::allocator<char> > __cdecl std::operator+<char,struct 
std::char_traits<char>,class std::allocator<char> >(class 
std::basic_string<char,struct std::char_traits<char>,class 
std::allocator<char> > const &,class std::basic_string<char,struct 
std::char_traits<char>,class std::allocator<char> > const &)" 
(??$?HDU?$char_traits@D@std@@V?$allocator@D@1@@std@@YA?AV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@0@ABV10@0@Z) 
already defined in FixApp.obj
1>msvcprt.lib(MSVCP80.dll) : error LNK2005: "class 
std::basic_string<char,struct std::char_traits<char>,class 
std::allocator<char> > __cdecl std::operator+<char,struct 
std::char_traits<char>,class std::allocator<char> >(class 
std::basic_string<char,struct std::char_traits<char>,class 
std::allocator<char> > const &,char const *)" 
(??$?HDU?$char_traits@D@std@@V?$allocator@D@1@@std@@YA?AV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@0@ABV10@PBD@Z) 
already defined in FixApp.obj
1>msvcprt.lib(MSVCP80.dll) : error LNK2005: "public: __thiscall 
std::basic_string<char,struct std::char_traits<char>,class 
std::allocator<char> >::basic_string<char,struct 
std::char_traits<char>,class std::allocator<char> >(char const *)" 
(??0?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QAE@PBD@Z) 
already defined in FixApp.obj
1>msvcprt.lib(MSVCP80.dll) : error LNK2005: "public: __thiscall 
std::basic_string<char,struct std::char_traits<char>,class 
std::allocator<char> >::basic_string<char,struct 
std::char_traits<char>,class std::allocator<char> >(void)" 
(??0?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QAE@XZ) 
already defined in FixApp.obj
1>msvcprt.lib(MSVCP80.dll) : error LNK2005: "public: class 
std::basic_string<char,struct std::char_traits<char>,class 
std::allocator<char> > & __thiscall std::basic_string<char,struct 
std::char_traits<char>,class std::allocator<char> >::operator=(class 
std::basic_string<char,struct std::char_traits<char>,class 
std::allocator<char> > const &)" 
(??4?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QAEAAV01@ABV01@@Z) 
already defined in FixApp.obj
1>msvcprt.lib(MSVCP80.dll) : error LNK2005: "public: class 
std::basic_string<char,struct std::char_traits<char>,class 
std::allocator<char> > & __thiscall std::basic_string<char,struct 
std::char_traits<char>,class std::allocator<char> >::assign(char const 
*,unsigned int)" 
(?assign@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QAEAAV12@PBDI@Z) 
already defined in FixApp.obj
1>msvcprt.lib(MSVCP80.dll) : error LNK2005: "public: class 
std::basic_string<char,struct std::char_traits<char>,class 
std::allocator<char> > & __thiscall std::basic_string<char,struct 
std::char_traits<char>,class std::allocator<char> >::operator+=(class 
std::basic_string<char,struct std::char_traits<char>,class 
std::allocator<char> > const &)" 
(??Y?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QAEAAV01@ABV01@@Z) 
already defined in FixApp.obj
1>msvcprt.lib(MSVCP80.dll) : error LNK2005: "public: __thiscall 
std::basic_string<char,struct std::char_traits<char>,class 
std::allocator<char> >::basic_string<char,struct 
std::char_traits<char>,class std::allocator<char> >(unsigned int,char)" 
(??0?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QAE@ID@Z) 
already defined in libcpmtd.lib(cout.obj)
1>msvcprt.lib(MSVCP80.dll) : error LNK2005: "class 
std::basic_ostream<char,struct std::char_traits<char> > & __cdecl 
std::operator<<<char,struct std::char_traits<char>,class 
std::allocator<char> >(class std::basic_ostream<char,struct 
std::char_traits<char> > &,class std::basic_string<char,struct 
std::char_traits<char>,class std::allocator<char> > const &)" 
(??$?6DU?$char_traits@D@std@@V?$allocator@D@1@@std@@YAAAV?$basic_ostream@DU?$char_traits@D@std@@@0@AAV10@ABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@0@@Z) 
already defined in FixApp.obj
1>msvcprt.lib(MSVCP80.dll) : error LNK2005: "bool __cdecl 
std::operator==<char,struct std::char_traits<char>,class 
std::allocator<char> >(class std::basic_string<char,struct 
std::char_traits<char>,class std::allocator<char> > const &,char const *)" 
(??$?8DU?$char_traits@D@std@@V?$allocator@D@1@@std@@YA_NABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@0@PBD@Z) 
already defined in FixApp.obj
1>msvcprt.lib(MSVCP80.dll) : error LNK2005: "public: void __thiscall 
std::_Mutex::_Lock(void)" (?_Lock@_Mutex@std@@QAEXXZ) already defined in 
libcpmtd.lib(xmutex.obj)
1>msvcprt.lib(MSVCP80.dll) : error LNK2005: "public: void __thiscall 
std::_Mutex::_Unlock(void)" (?_Unlock@_Mutex@std@@QAEXXZ) already defined 
in libcpmtd.lib(xmutex.obj)
1>msvcprt.lib(MSVCP80.dll) : error LNK2005: "public: class 
std::basic_string<char,struct std::char_traits<char>,class 
std::allocator<char> > __thiscall std::basic_string<char,struct 
std::char_traits<char>,class std::allocator<char> >::substr(unsigned 
int,unsigned int)const " 
(?substr@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QBE?AV12@II@Z) 
already defined in FixApp.obj
1>msvcprt.lib(MSVCP80.dll) : error LNK2005: "public: unsigned int 
__thiscall std::basic_string<char,struct std::char_traits<char>,class 
std::allocator<char> >::find(char const *,unsigned int,unsigned int)const 
" 
(?find@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QBEIPBDII@Z) 
already defined in FixApp.obj
1>msvcprt.lib(MSVCP80.dll) : error LNK2005: "public: class 
std::basic_ostream<char,struct std::char_traits<char> > & __thiscall 
std::basic_ostream<char,struct std::char_traits<char> >::flush(void)" 
(?flush@?$basic_ostream@DU?$char_traits@D@std@@@std@@QAEAAV12@XZ) already 
defined in FixApp.obj
1>msvcprt.lib(MSVCP80.dll) : error LNK2005: "public: void __thiscall 
std::basic_ostream<char,struct std::char_traits<char> >::_Osfx(void)" 
(?_Osfx@?$basic_ostream@DU?$char_traits@D@std@@@std@@QAEXXZ) already 
defined in FixApp.obj
1>msvcprt.lib(MSVCP80.dll) : error LNK2005: "bool __cdecl 
std::uncaught_exception(void)" (?uncaught_exception@std@@YA_NXZ) already 
defined in libcpmtd.lib(uncaught.obj)
1>msvcprt.lib(MSVCP80.dll) : error LNK2005: "public: void __thiscall 
std::basic_ios<char,struct std::char_traits<char> >::setstate(int,bool)" 
(?setstate@?$basic_ios@DU?$char_traits@D@std@@@std@@QAEXH_N@Z) already 
defined in FixApp.obj
1>msvcprt.lib(MSVCP80.dll) : error LNK2005: "public: int __thiscall 
std::basic_streambuf<char,struct std::char_traits<char> >::sputn(char 
const *,int)" 
(?sputn@?$basic_streambuf@DU?$char_traits@D@std@@@std@@QAEHPBDH@Z) already 
defined in FixApp.obj
1>msvcprt.lib(MSVCP80.dll) : error LNK2005: "public: int __thiscall 
std::basic_streambuf<char,struct std::char_traits<char> >::sputc(char)" 
(?sputc@?$basic_streambuf@DU?$char_traits@D@std@@@std@@QAEHD@Z) already 
defined in FixApp.obj
1>msvcprt.lib(MSVCP80.dll) : error LNK2005: "class 
std::basic_string<char,struct std::char_traits<char>,class 
std::allocator<char> > __cdecl std::operator+<char,struct 
std::char_traits<char>,class std::allocator<char> >(char const *,class 
std::basic_string<char,struct std::char_traits<char>,class 
std::allocator<char> > const &)" 
(??$?HDU?$char_traits@D@std@@V?$allocator@D@1@@std@@YA?AV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@0@PBDABV10@@Z) 
already defined in FixApp.obj
1>msvcprt.lib(MSVCP80.dll) : error LNK2005: "public: class 
std::basic_string<char,struct std::char_traits<char>,class 
std::allocator<char> > & __thiscall std::basic_string<char,struct 
std::char_traits<char>,class std::allocator<char> >::operator=(char const 
*)" 
(??4?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QAEAAV01@PBD@Z) 
already defined in FixApp.obj
1>msvcprt.lib(MSVCP80.dll) : error LNK2005: "public: class 
std::_String_iterator<char,struct std::char_traits<char>,class 
std::allocator<char> > __thiscall std::basic_string<char,struct 
std::char_traits<char>,class std::allocator<char> >::begin(void)" 
(?begin@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QAE?AV?$_String_iterator@DU?$char_traits@D@std@@V?$allocator@D@2@@2@XZ) 
already defined in libcpmtd.lib(cout.obj)
1>msvcprt.lib(MSVCP80.dll) : error LNK2005: "public: class 
std::basic_string<char,struct std::char_traits<char>,class 
std::allocator<char> > & __thiscall std::basic_string<char,struct 
std::char_traits<char>,class std::allocator<char> >::append(char const 
*,unsigned int)" 
(?append@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QAEAAV12@PBDI@Z) 
already defined in FixApp.obj
1>msvcprt.lib(MSVCP80.dll) : error LNK2005: "public: __thiscall 
std::basic_string<char,struct std::char_traits<char>,class 
std::allocator<char> >::basic_string<char,struct 
std::char_traits<char>,class std::allocator<char> >(class 
std::basic_string<char,struct std::char_traits<char>,class 
std::allocator<char> > const &,unsigned int,unsigned int)" 
(??0?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QAE@ABV01@II@Z) 
already defined in FixApp.obj
1>msvcprt.lib(MSVCP80.dll) : error LNK2005: "public: class 
std::basic_string<char,struct std::char_traits<char>,class 
std::allocator<char> > & __thiscall std::basic_string<char,struct 
std::char_traits<char>,class std::allocator<char> >::erase(unsigned 
int,unsigned int)" 
(?erase@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QAEAAV12@II@Z) 
already defined in FixApp.obj
1>msvcprt.lib(MSVCP80.dll) : error LNK2005: "public: class 
std::basic_string<char,struct std::char_traits<char>,class 
std::allocator<char> > & __thiscall std::basic_string<char,struct 
std::char_traits<char>,class std::allocator<char> >::operator+=(char const 
*)" 
(??Y?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QAEAAV01@PBD@Z) 
already defined in FixApp.obj
1>msvcprt.lib(MSVCP80.dll) : error LNK2005: "public: unsigned int 
__thiscall std::basic_string<char,struct std::char_traits<char>,class 
std::allocator<char> >::rfind(char const *,unsigned int,unsigned int)const 
" 
(?rfind@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QBEIPBDII@Z) 
already defined in FixApp.obj
1>MSVCRT.lib(MSVCR80.dll) : error LNK2005: "public: __thiscall 
std::exception::exception(char const * const &)" 
(??0exception@std@@QAE@ABQBD@Z) already defined in 
LIBCMTD.lib(stdexcpt.obj)
1>MSVCRT.lib(MSVCR80.dll) : error LNK2005: "public: virtual __thiscall 
std::exception::~exception(void)" (??1exception@std@@UAE@XZ) already 
defined in LIBCMTD.lib(stdexcpt.obj)
1>MSVCRT.lib(MSVCR80.dll) : error LNK2005: "public: __thiscall 
std::exception::exception(void)" (??0exception@std@@QAE@XZ) already 
defined in LIBCMTD.lib(stdexcpt.obj)
1>MSVCRT.lib(MSVCR80.dll) : error LNK2005: "public: __thiscall 
std::exception::exception(class std::exception const &)" 
(??0exception@std@@QAE@ABV01@@Z) already defined in 
LIBCMTD.lib(stdexcpt.obj)
1>MSVCRT.lib(MSVCR80.dll) : error LNK2005: _vsprintf_s already defined in 
LIBCMTD.lib(vsnprnc.obj)
1>MSVCRT.lib(MSVCR80.dll) : error LNK2005: _memmove_s already defined in 
LIBCMTD.lib(memmove_s.obj)
1>MSVCRT.lib(MSVCR80.dll) : error LNK2005: _strchr already defined in 
LIBCMTD.lib(strchr.obj)
1>MSVCRT.lib(MSVCR80.dll) : error LNK2005: _isdigit already defined in 
LIBCMTD.lib(_ctype.obj)
1>MSVCRT.lib(MSVCR80.dll) : error LNK2005: _fflush already defined in 
LIBCMTD.lib(fflush.obj)
1>MSVCRT.lib(MSVCR80.dll) : error LNK2005: _fseek already defined in 
LIBCMTD.lib(fseek.obj)
1>MSVCRT.lib(MSVCR80.dll) : error LNK2005: _fclose already defined in 
LIBCMTD.lib(fclose.obj)
1>MSVCRT.lib(MSVCR80.dll) : error LNK2005: _fwrite already defined in 
LIBCMTD.lib(fwrite.obj)
1>MSVCRT.lib(MSVCR80.dll) : error LNK2005: _ftell already defined in 
LIBCMTD.lib(ftell.obj)
1>MSVCRT.lib(MSVCR80.dll) : error LNK2005: _tolower already defined in 
LIBCMTD.lib(tolower.obj)
1>MSVCRT.lib(MSVCR80.dll) : error LNK2005: _atol already defined in 
LIBCMTD.lib(atox.obj)
1>MSVCRT.lib(MSVCR80.dll) : error LNK2005: _strtol already defined in 
LIBCMTD.lib(strtol.obj)
1>MSVCRT.lib(MSVCR80.dll) : error LNK2005: "public: class std::exception & 
__thiscall std::exception::operator=(class std::exception const &)" 
(??4exception@std@@QAEAAV01@ABV01@@Z) already defined in 
LIBCMTD.lib(stdexcpt.obj)
1>MSVCRT.lib(MSVCR80.dll) : error LNK2005: _malloc already defined in 
LIBCMTD.lib(dbgheap.obj)
1>MSVCRT.lib(MSVCR80.dll) : error LNK2005: _realloc already defined in 
LIBCMTD.lib(dbgheap.obj)
1>MSVCRT.lib(MSVCR80.dll) : error LNK2005: _free already defined in 
LIBCMTD.lib(dbgheap.obj)
1>MSVCRT.lib(MSVCR80.dll) : error LNK2005: _exit already defined in 
LIBCMTD.lib(crt0dat.obj)
1>MSVCRT.lib(ti_inst.obj) : error LNK2005: "private: __thiscall 
type_info::type_info(class type_info const &)" (??0type_info@@AAE@ABV0@@Z) 
already defined in LIBCMTD.lib(typinfo.obj)
1>MSVCRT.lib(ti_inst.obj) : error LNK2005: "private: class type_info & 
__thiscall type_info::operator=(class type_info const &)" 
(??4type_info@@AAEAAV0@ABV0@@Z) already defined in 
LIBCMTD.lib(typinfo.obj)
1>LINK : warning LNK4098: defaultlib 'MSVCRT' conflicts with use of other 
libs; use /NODEFAULTLIB:library
1>C:\Documents and Settings\gchabala\My Documents\Visual Studio 
2005\Projects\fix-test-connection\Debug\fix-test-connection.exe : fatal 
error LNK1169: one or more multiply defined symbols found
1>Build log was saved at "file://c:\Documents and Settings\gchabala\My 
Documents\Visual Studio 
2005\Projects\fix-test-connection\Debug\BuildLog.htm"
1>fix-test-connection - 54 error(s), 1 warning(s)
========== Rebuild All: 0 succeeded, 1 failed, 0 skipped ==========

I believe part of it is conflicts with MSVCRT.lib, but I've tried using 
/NODEFAULTLIB:MSVCRT.lib in the linker options to no avail.

Greg Chabala





Oren Miller <or...@qu...> 
10/18/2006 05:08 PM

To
Gre...@Ca...
cc
qui...@li...
Subject
Re: [Quickfix-users] Trouble compiling, linker errors






Please post your linker errors to the list.

--oren

On Oct 18, 2006, at 4:15 PM, Gre...@Ca... wrote:

Now it's time for me to get the original program running again so that I 
may expand on it, but I have not been able to get it to compile without 
linker errors. I followed the directions in the html documentation to add 
the libs to the project and added another include directory to point to 
the quickfix source. I also tried someone's suggestion to go ahead and add 
all the Quickfix source to my project, but this has not helped. 


-- 
This communication may contain privileged and/or confidential information 
and is intended solely for the addressee.  No waiver of confidentiality or 
privilege is made by mistransmission.  If you are not the intended 
recipient, you are hereby notified that any unauthorized dissemination, 
distribution, reading, printing, copying and/or use of this communication 
is strictly prohibited. If you have received this communication in error, 
please delete this message and immediately notify the sender by return 
e-mail.  Calyon Financial Inc. makes no representation or warranty 
regarding the correctness of any information contained herein, or the 
appropriateness of any transaction for any person. Nothing herein shall be 
construed as a recommendation to buy or sell any financial instrument or 
security. This communication is for informational purposes only.  Unless 
expressly stated, opinions in this e-mail are those of the individual 
sender and not of the Calyon Financial Group. For further information 
about the Calyon Financial Group, please see our website at 
http://www.calyonfinancial.com 

[Quickfix-users] Incorrect value for Tag 555

[<San...@ub...>]

Visit our website at http://www.ubs.com

This message contains confidential information and is intended only 
for the individual named.  If you are not the named addressee you 
should not disseminate, distribute or copy this e-mail.  Please 
notify the sender immediately by e-mail if you have received this 
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free 
as information could be intercepted, corrupted, lost, destroyed, 
arrive late or incomplete, or contain viruses.  The sender therefore 
does not accept liability for any errors or omissions in the contents 
of this message which arise as a result of e-mail transmission.  If 
verification is required please request a hard-copy version.  This 
message is provided for informational purposes and should not be 
construed as a solicitation or offer to buy or sell any securities or 
related financial instruments.

Re: [Quickfix-users] Trouble compiling, linker errors

[Oren M. <or...@qu...>]

Please post your linker errors to the list.

--oren

On Oct 18, 2006, at 4:15 PM, Gre...@Ca... wrote:

> Now it's time for me to get the original program running again so  
> that I may expand on it, but I have not been able to get it to  
> compile without linker errors. I followed the directions in the  
> html documentation to add the libs to the project and added another  
> include directory to point to the quickfix source. I also tried  
> someone's suggestion to go ahead and add all the Quickfix source to  
> my project, but this has not helped.

[Quickfix-users] Trouble compiling, linker errors

[<Gre...@Ca...>]

Hello all,

I am having beginners difficulty compiling a Quickfix program. Here is my 
situation:

I am holding a simple Quickfix program that someone else wrote, but it did 
not include the required library files to build it. At the time I first 
received it, I wrote a version of it in java using Quickfix/J, which was 
successful.

Now it's time for me to get the original program running again so that I 
may expand on it, but I have not been able to get it to compile without 
linker errors. I followed the directions in the html documentation to add 
the libs to the project and added another include directory to point to 
the quickfix source. I also tried someone's suggestion to go ahead and add 
all the Quickfix source to my project, but this has not helped.

I'm using Visual Studio 2005, and I'm trying to make a Win32 Console app 
in C++, so I shouldn't have to include the .Net dlls. I've tried using the 
VS8 1.12.4 bin, as well as the VS6, and the source distribution, although 
I didn't try to build the library myself, because I don't want to.

What advise can you offer me? Does anyone have a step by step guide to 
ensure success?


Greg Chabala

-- 
This communication may contain privileged and/or confidential information 
and is intended solely for the addressee.  No waiver of confidentiality or 
privilege is made by mistransmission.  If you are not the intended 
recipient, you are hereby notified that any unauthorized dissemination, 
distribution, reading, printing, copying and/or use of this communication 
is strictly prohibited. If you have received this communication in error, 
please delete this message and immediately notify the sender by return 
e-mail.  Calyon Financial Inc. makes no representation or warranty 
regarding the correctness of any information contained herein, or the 
appropriateness of any transaction for any person. Nothing herein shall be 
construed as a recommendation to buy or sell any financial instrument or 
security. This communication is for informational purposes only.  Unless 
expressly stated, opinions in this e-mail are those of the individual 
sender and not of the Calyon Financial Group. For further information 
about the Calyon Financial Group, please see our website at 
http://www.calyonfinancial.com 

Re: [Quickfix-users] Testing Quickfix .NET API with NUnit Framework

[Oren M. <or...@qu...>]

Is the test something you would be able to send me so I can tell what  
is going on?  It looks like it has something to do with NUnit  
creating appdomains.  It would be nice to be able to replicate the  
problem with a simple test that just uses QuickFIX.

--oren

On Oct 17, 2006, at 1:32 PM, Greg Snow wrote:

> Oren
>
> I just rebuilt with the latest QuickFIX release (1.12.4) and got  
> the same error.  Have you heard of other people having a similar  
> problem before?  It seems like it has happened before (http:// 
> sourceforge.net/mailarchive/message.php?msg_id=10062941).  It looks  
> like some sort of issue with garbage collection and managed/ 
> unmanaged code.  The strange this is that it only happens when  
> testing against NUnit.  Any other ideas?

Re: [Quickfix-users] Testing Quickfix .NET API with NUnit Framework

[Greg S. <gre...@ch...>]

Oren

=20

I just rebuilt with the latest QuickFIX release (1.12.4) and got the
same error.  Have you heard of other people having a similar problem
before?  It seems like it has happened before
(http://sourceforge.net/mailarchive/message.php?msg_id=3D10062941
<http://sourceforge.net/mailarchive/message.php?msg_id=3D10062941> ).  =
It
looks like some sort of issue with garbage collection and
managed/unmanaged code.  The strange this is that it only happens when
testing against NUnit.  Any other ideas?

=20

Thanks,

Greg

=20

________________________________

From: Oren Miller [mailto:or...@qu...]=20
Sent: Tuesday, October 17, 2006 10:24 AM
To: Greg Snow
Cc: qui...@li...;
qui...@li...
Subject: Re: [Quickfix-users] Testing Quickfix .NET API with NUnit
Framework

=20

Is it possible you can try this with the latest release?

=20

--oren

=20

On Oct 17, 2006, at 8:43 AM, Greg Snow wrote:





We have an application using the QuickFix .NET API (Quickfix version
1.10.2).  When trying to run unit tests using the NUnit framework, we
are getting exceptions of the type 'System.ArgumentException : Cannot
pass GCHandle across app domains.'  At first, it appeared to be a bug in
our code, but that doesn't seem to be the case.  This exception only
occurs when unit testing with NUnit.  We can compile to an executable
and the same code runs without errors.

 The exception is being thrown from mscorlib.dll (line 118 of the
gcroot.h header).  The function throwing the exception and the
debugger's stack trace are attached in a text file.

 I have also come across another develop with the exact same problem
(his initial post is here:
http://sourceforge.net/mailarchive/message.php?msg_id=3D10062941).  I
contacted him and he said that he never came up with a solution and was
forced to write his own FIX implementation.  Any help on this issue
would be appreciated.  Thanks.




This message is intended only for the personal and confidential use of =
the recipients named above. If the reader of this email is not the =
intended recipient, you have received this email in error and any =
review, dissemination, distribution or copying is strictly prohibited. =
If you have received this email in error, please notify the sender =
immediately by return email and permanently delete the copy you =
received.=20

This message is provided for informational purposes and should not be =
construed as a solicitation or offer to buy or sell any securities or =
related financial instruments. CTC Holdings nor any affiliates ("CTC") =
are responsible for any recommendation, solicitation, offer or agreement =
or any information about any transaction, customer account or account =
activity that may be attached to or contained in this communication. CTC =
accepts no liability for any content contained in the email, or any =
errors or omissions arising as a result of e-mail transmission. Any =
opinions contained in this email constitute the sender's best judgment =
at this time and are subject to change without notice.=20

=20

Re: [Quickfix-users] Testing Quickfix .NET API with NUnit Framework

[Oren M. <or...@qu...>]

Is it possible you can try this with the latest release?

--oren

On Oct 17, 2006, at 8:43 AM, Greg Snow wrote:

> We have an application using the QuickFix .NET API (Quickfix =20
> version 1.10.2).  When trying to run unit tests using the NUnit =20
> framework, we are getting exceptions of the type =20
> =91System.ArgumentException : Cannot pass GCHandle across app =20
> domains.=92  At first, it appeared to be a bug in our code, but that =20=

> doesn=92t seem to be the case.  This exception only occurs when unit =20=

> testing with NUnit.  We can compile to an executable and the same =20
> code runs without errors.
>
>  The exception is being thrown from mscorlib.dll (line 118 of the =20
> gcroot.h header).  The function throwing the exception and the =20
> debugger=92s stack trace are attached in a text file.
>
>  I have also come across another develop with the exact same =20
> problem (his initial post is here: http://sourceforge.net/=20
> mailarchive/message.php?msg_id=3D10062941).  I contacted him and he =20=

> said that he never came up with a solution and was forced to write =20
> his own FIX implementation.  Any help on this issue would be =20
> appreciated.  Thanks.

[Quickfix-users] Testing Quickfix .NET API with NUnit Framework

[Greg S. <gre...@ch...>]

VGhpcyBpcyB0aGUgZnVuY3Rpb24gd2hlcmUgdGhlIHVuaGFuZGxlZCBleGNlcHRpb24gb2NjdXJz
IChMaW5lIDExOCBvZiBnY3Jvb3QuaCkuDQoNCjExNiBUIG9wZXJhdG9yLT4oKSBjb25zdCB7DQox
MTcgICAvLyBnY3Jvb3QgaXMgdHlwZXNhZmUsIHNvIHVzZSBzdGF0aWNfY2FzdA0KMTE4IHJldHVy
biBzdGF0aWNfY2FzdDxUPihHQ0hhbmRsZTo6b3BfRXhwbGljaXQoX2hhbmRsZSkuVGFyZ2V0KTsN
Cg0KDQpIZXJlIGlzIHRoZSBkZWJ1Z2dlcidzIHN0YWNrIHRyYWNlICh0aGlzIGV4dGVuZGVkIHN0
YWNrIHRyYWNlIHdhcyBhZnRlciAnRW5hYmxlIFVubWFuYWdlZA0KICBEZWJ1Z2dpbmcnIHdhcyB0
dXJuZWQgb24gZm9yIGFsbCBwcm9qZWN0cyBpbiB0aGUgc29sdXRpb24pDQoNCm1zY29ybGliLmRs
bCFTeXN0ZW0uUnVudGltZS5JbnRlcm9wU2VydmljZXMuR0NIYW5kbGUoaW50IGhhbmRsZSA9IDE4
ODc5NjcyKSArIDB4MWEgYnl0ZXMNCm1zY29ybGliLmRsbCFTeXN0ZW0uUnVudGltZS5JbnRlcm9w
U2VydmljZXMub3BfRXhjcGxpY2l0KGludCB2YWx1ZSA9IDE4ODc5NjcyKSArIDB4MTMgYnl0ZXMN
CnF1aWNrZml4X25ldC5kbGwhZ2Nyb290PFF1aWNrRml4OjpMb2dfX2djKj46Om9wZXJhdG9yLT4o
KSBMaW5lIDExOCArIDB4MWMgYnl0ZXMNCnF1aWNrZml4X25ldC5kbGwhTG9nOjpvbkV2ZW50KHN0
ZDo6YmFzaWNfc3RyaW5nPGNoYXIsc3RkOjpjaGFyX3RyYWl0czxjaGFyPixzdGQ6OmFsbG9jYXRv
cjxjaGFyPj4mc3RyaW5nPXsuLi59KUxpbmUgNTIgKyAweDkNCnF1aWNrZml4X25ldC5kbGwhRklY
OjpTZXNzaW9uU3RhdGU6Om9uRXZlbnQoQ29uc3Qgc3RkOjpiYXNpY19zdHJpbmc8Y2hhciwgc3Rk
OjpjaGFyX3RyYWl0czxjaGFyPiwgc3RkOjphbGxvY2F0b3I8Y2hhcj4+ICYgc3RyaW5nPXsuLi59
KSBMaW5lIDE4MSArIDB4NzYNCnF1aWNrZml4X25ldC5kbGwhRklYOjpUaHJlYWRlZFNvY2tldElu
aXRpYXRvcjo6c29ja2V0VGhyZWFkKHZvaWQgKiBwID0gMHgwNDRlZjI0OCkgTGluZSAxOTUgKyAw
eGRjDQptc3ZjcjcxLmRsbCFfdGhyZWFkc3RhcnRleCh2b2lkICogcHRkPTB4NTJkMTA5MCkgTGlu
ZSAyNDEgKyAweGQNCg0KDQoNCg==

Re: [Quickfix-users] MSSQL in 1.12.4

[Oren M. <or...@qu...>]

Direct MSSQL support has been deprecated in favor of ODBC support.   
You should use ODBC to interact with MSSQL.  We have deprecated the  
use of the mssql c library because Microsoft had deprecated it.

--oren

On Oct 16, 2006, at 6:22 PM, David Z wrote:

> QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/ 
> html/index.html
> QuickFIX Support: http://www.quickfixengine.org/services.html
>
> It appears that 1.12.4 has deprecated support for
> MSSQL.  Was this intentional?
>
> Also the MemoryStoreFactory has disappeared.  Is this
> intentional or did someone forget to do a diff?
>
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
> ---------------------------------------------------------------------- 
> ---
> Using Tomcat but need to do more? Need to support web services,  
> security?
> Get stuff done quickly with pre-integrated technology to make your  
> job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache  
> Geronimo
> http://sel.as-us.falkag.net/sel? 
> cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Quickfix-users mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-users
>

[Quickfix-users] MSSQL in 1.12.4

[David Z <dav...@ya...>]

It appears that 1.12.4 has deprecated support for
MSSQL.  Was this intentional?  

Also the MemoryStoreFactory has disappeared.  Is this
intentional or did someone forget to do a diff?



__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

[Quickfix-users] How do I close acceptor socket in C#.net 2005

[Chris v. O. <chr...@gn...>]

Ive tried a few ways and they all seem to crash my app.... here is my 
latest attempt:

        delegate void D_StopSession();
        private void stopSession()
        {
            if (!InvokeRequired)
            {
                try
                {
                    this.acceptor.stop();
                }
                catch (Exception ex)
                {
                    MessageBox.Show("Exception: " + ex.Message);
                }
                this.SetConnectionState();
            }
            else
            {
                Invoke(new D_StopSession(stopSession),new object[]{});
            }
        }

I dont see any Exception but the application just hangs. I just want to 
close the socket. acceptor was created like:
                messageFactory = new DefaultMessageFactory();
                acceptor = new SocketAcceptor( App, storeFactory, 
settings, messageFactory );
and was tested for null and passed acceptor.IsConnected() before calling 
this method. My settings are....

[DEFAULT]
ConnectionType=acceptor
SocketAcceptPort=5001
SocketReuseAddress=Y
StartTime=00:00:00
EndTime=00:00:00

[SESSION]
BeginString=FIX.4.2
SenderCompID=ARCA
TargetCompID=TORC
FileStorePath=store
DataDictionary=C:/etc/FIX42.xml

Thanks, Chris

Re: [Quickfix-users] How do you know to use FIX::FileLogFactory?

[EclipseCap <tob...@ec...>]

Oren,

Thanks for the link.  From the number of postings I can tell that you do a
lot for this board.

When I evetually become versed in fix perhaps I will write up a document
helping beginners become more than beginners.  

Thanks for all of the help



Oren Miller wrote:
> 
> QuickFIX Documentation:
> http://www.quickfixengine.org/quickfix/doc/html/index.html
> QuickFIX Support: http://www.quickfixengine.org/services.html
> 
> It's all accessible from the documentation page: http:// 
> www.quickfixengine.org/documentation.html
> 
> The documentation is also distributed with the release in the doc/ 
> html directory.
> 
> --oren
> 
> On Oct 12, 2006, at 3:11 PM, EclipseCap wrote:
> 
>> QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/ 
>> html/index.html
>> QuickFIX Support: http://www.quickfixengine.org/services.html
>>
>> I have a question for the collective mind.  How did you know to use
>> FIX::FileLogFactory?  I am new to FIX and QuickFIX and only have the
>> examples as a development guide.  The examples for QuickFIX namely
>> tradingclient use the
>> FIX::ScreenLogFactory.
>>
>> How is a new programmer to QFix going to know to look for other  
>> logging
>> options?
> 
> 
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job
> easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Quickfix-users mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-users
> 
> 

-- 
View this message in context: http://www.nabble.com/How-do-you-know-to-use-FIX%3A%3AFileLogFactory--tf2432817.html#a6784885
Sent from the QuickFIX - User mailing list archive at Nabble.com.

Re: [Quickfix-users] How do you know to use FIX::FileLogFactory?

[Oren M. <or...@qu...>]

It's all accessible from the documentation page: http:// 
www.quickfixengine.org/documentation.html

The documentation is also distributed with the release in the doc/ 
html directory.

--oren

On Oct 12, 2006, at 3:11 PM, EclipseCap wrote:

> QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/ 
> html/index.html
> QuickFIX Support: http://www.quickfixengine.org/services.html
>
> I have a question for the collective mind.  How did you know to use
> FIX::FileLogFactory?  I am new to FIX and QuickFIX and only have the
> examples as a development guide.  The examples for QuickFIX namely
> tradingclient use the
> FIX::ScreenLogFactory.
>
> How is a new programmer to QFix going to know to look for other  
> logging
> options?