quickfix-developers — QuickFIX developers forum

Re: [Quickfix-developers] quickfix_jni not built on Linux

[<OM...@th...>]

Here is the test application we had written that demonstrated the behavior
we have been seeing.  If we can get this program to work properly, we can
most likely solve our JNI problem under linux.

(See attached file: exception.tar.gz)

--oren


|---------+----------------------------------------------->
|         |           JDD...@th...           |
|         |           Sent by:                            |
|         |           qui...@li...ur|
|         |           ceforge.net                         |
|         |                                               |
|         |                                               |
|         |           06/19/2002 01:13 PM                 |
|         |                                               |
|---------+----------------------------------------------->
  >----------------------------------------------------------------------------------------------|
  |                                                                                              |
  |       To:       qui...@li...                                    |
  |       cc:                                                                                    |
  |       Subject:  Re: [Quickfix-developers] quickfix_jni not built on Linux                    |
  >----------------------------------------------------------------------------------------------|





Alex,

You seem to be describing the behavior we have seen. When we started
developing QuickFIX, we intended to build both static and shared objects
for Linux. Our test application was aborting and, with a little research on
the web and a test application, we attributed the problem to Linux not
having operating-system structured exception handling support.

Do you have another application that is throwing and catching an exception
within a shared library? We'd really like to have a workaround for this
problem. Oren will send out the code for a little program that demonstrates
the behavior we have seen.

John Duncan
Collaborative Development Group
Thoughtworks, Inc
+1 (312) 953 6286



                      Alex Hornby <al...@an...>

                      Sent by:                                    To:
JDD...@th...
                      qui...@li...ur        cc:
quickfix-developers <qui...@li...>
                      ceforge.net                                 Subject:
Re: [Quickfix-developers] quickfix_jni not built on Linux


                      06/19/2002 12:34 PM







On Wed, 2002-06-19 at 17:35, JDD...@th... wrote:
>
>
> Alex,
>
> We haven't ported the JNI code to Unix systems yet. The Solaris port, if
> anyone asks for it, will be the easiest to finish. Unfortunately, Linux
> doesn't support C++ exceptions in shared objects so we are going to have
to
> make some major modifications to get it running there.
>
> We can give you support to get this done, if you'd like, or we can offer
> our professional services to your company.
>
> Sorry,
> John Duncan
>

Hi John,

AFAIK Linux supports C++ exceptions in shared objects in (I'm using them
right now). It there a QuickFix or Java specific problem?

BTW I've got the JNI module built but Banzai aborts when it starts up.
Perhaps the exceptions are the problem?

Alex.




----------------------------------------------------------------------------


                   Bringing you mounds of caffeinated joy
                   >>>     http://thinkgeek.com/sf    <<<

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





----------------------------------------------------------------------------

                   Bringing you mounds of caffeinated joy
                   >>>     http://thinkgeek.com/sf    <<<

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

Re: [Quickfix-developers] quickfix_jni not built on Linux

[<JDD...@th...>]

Alex,

You seem to be describing the behavior we have seen. When we started
developing QuickFIX, we intended to build both static and shared objects
for Linux. Our test application was aborting and, with a little research on
the web and a test application, we attributed the problem to Linux not
having operating-system structured exception handling support.

Do you have another application that is throwing and catching an exception
within a shared library? We'd really like to have a workaround for this
problem. Oren will send out the code for a little program that demonstrates
the behavior we have seen.

John Duncan
Collaborative Development Group
Thoughtworks, Inc
+1 (312) 953 6286


                                                                                                                                                    
                      Alex Hornby <al...@an...>                                                                                                
                      Sent by:                                    To:       JDD...@th...                                               
                      qui...@li...ur        cc:       quickfix-developers <qui...@li...>         
                      ceforge.net                                 Subject:  Re: [Quickfix-developers] quickfix_jni not built on Linux               
                                                                                                                                                    
                                                                                                                                                    
                      06/19/2002 12:34 PM                                                                                                           
                                                                                                                                                    
                                                                                                                                                    




On Wed, 2002-06-19 at 17:35, JDD...@th... wrote:
>
>
> Alex,
>
> We haven't ported the JNI code to Unix systems yet. The Solaris port, if
> anyone asks for it, will be the easiest to finish. Unfortunately, Linux
> doesn't support C++ exceptions in shared objects so we are going to have
to
> make some major modifications to get it running there.
>
> We can give you support to get this done, if you'd like, or we can offer
> our professional services to your company.
>
> Sorry,
> John Duncan
>

Hi John,

AFAIK Linux supports C++ exceptions in shared objects in (I'm using them
right now). It there a QuickFix or Java specific problem?

BTW I've got the JNI module built but Banzai aborts when it starts up.
Perhaps the exceptions are the problem?

Alex.




----------------------------------------------------------------------------

                   Bringing you mounds of caffeinated joy
                   >>>     http://thinkgeek.com/sf    <<<

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

Re: [Quickfix-developers] quickfix_jni not built on Linux

[Alex H. <al...@an...>]

On Wed, 2002-06-19 at 17:35, JDD...@th... wrote:
> 
> 
> Alex,
> 
> We haven't ported the JNI code to Unix systems yet. The Solaris port, if
> anyone asks for it, will be the easiest to finish. Unfortunately, Linux
> doesn't support C++ exceptions in shared objects so we are going to have to
> make some major modifications to get it running there.
> 
> We can give you support to get this done, if you'd like, or we can offer
> our professional services to your company.
> 
> Sorry,
> John Duncan
> 

Hi John,

AFAIK Linux supports C++ exceptions in shared objects in (I'm using them
right now). It there a QuickFix or Java specific problem?

BTW I've got the JNI module built but Banzai aborts when it starts up.
Perhaps the exceptions are the problem?

Alex.

Re: [Quickfix-developers] quickfix_jni not built on Linux

[<JDD...@th...>]

Alex,

We haven't ported the JNI code to Unix systems yet. The Solaris port, if
anyone asks for it, will be the easiest to finish. Unfortunately, Linux
doesn't support C++ exceptions in shared objects so we are going to have to
make some major modifications to get it running there.

We can give you support to get this done, if you'd like, or we can offer
our professional services to your company.

Sorry,
John Duncan

Thoughtworks, Inc
+1 (312) 953 6286


                                                                                                                                                    
                      Alex Hornby <al...@an...>                                                                                                
                      Sent by:                                    To:       qui...@li...                               
                      qui...@li...ur        cc:                                                                               
                      ceforge.net                                 Subject:  [Quickfix-developers] quickfix_jni not built on Linux                   
                                                                                                                                                    
                                                                                                                                                    
                      06/19/2002 11:20 AM                                                                                                           
                                                                                                                                                    
                                                                                                                                                    




Hi,

The quickfix JNI lib doesn't get built on Linux as there is nothing in
the Makefile.am.

All the rest of the java stuff builds (banzai etc.). Is anyone looking
at this?

Cheers,
Alex.



----------------------------------------------------------------------------

                   Bringing you mounds of caffeinated joy
                   >>>     http://thinkgeek.com/sf    <<<

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

[Quickfix-developers] quickfix_jni not built on Linux

[Alex H. <al...@an...>]

Hi,

The quickfix JNI lib doesn't get built on Linux as there is nothing in
the Makefile.am.

All the rest of the java stuff builds (banzai etc.). Is anyone looking
at this?

Cheers,
Alex. 

RE: [Quickfix-developers] Version 1.1.0 is available!

[<OM...@th...>]

Yeah, although the tradeclient application supports 4.0, 4.1, and 4.2, the
ordermatch application only supports 4.2. (you are trying to send 4.1
messages to it).
You can change it to support 4.1 easily enough if you want to, but we only
implemented as 4.2 for the example.

--oren


                                                                                                                                       
                      Justin Pauley                                                                                                    
                      <jp...@fs...>        To:       OM...@th...                                                      
                                               cc:       qui...@li...,                                    
                      06/12/2002 08:47          qui...@li...                                        
                      PM                       Subject:  RE: [Quickfix-developers] Version 1.1.0 is available!                         
                                                                                                                                       
                                                                                                                                       




Oi! Your suggestion worked and I got it compiled and installed (I only
have libxml2 installed btw and I have
/usr/local/share/aclocal/libxml.m4)


I no longer have the segfault problem (except when I run tradeclient
without a file (once by mistake)). Now, however, I have a new problem. I
run ordermatch and tradeclient and it connects and tradeclient sends
login and stuff and after I enter an order tradeclient does the: OUT:
8=FIX.4.19=9135=D34=249=direct5752=20020612-23:40:1756=IB11=000021=138=1
040=154=155=rhat59=010=164 and ordermatch does nothing other than
display:
Logout - BeginString: FIX.4.1, SenderCompID: IB, TargetCompID: direct57
Logout - BeginString: FIX.4.1, SenderCompID: IB, TargetCompID: direct57

I checked ordermatches log and I came up with this:
8=FIX.4.19=6135=A34=149=IB52=20020612-23:40:0156=direct5798=0108=3010=14
98=FIX.4.19=8235=334=249=IB52=20020612-23:40:1756=direct5745=258=Unsuppo
rted message type10=141

Any ideas?


Thanks,
Justin

-----Original Message-----
From: OM...@th... [mailto:OM...@th...]
Sent: Wednesday, June 12, 2002 6:07 PM
To: jp...@fs...
Cc: qui...@li...;
qui...@li...
Subject: RE: [Quickfix-developers] Version 1.1.0 is available!



heh, kind of funny.  libxml does the installation, checks it, and says
the installation is wrong.  Looks kind of like immovable object meets
irresistable force.  I'd like to hear from anyone else who has seen
this.

Do you have libxml and libxml-devel installed, or just libxml? Also
check to see if you have libxml.m4 somewhere on your system.  I just
want to know so I have the information.

In the interim you can probably just disable the script and not worry
about it.  In the confiure.in, comment out the AM_PATH_XML2 call, and
just manually set XML_LIBS and XML_CFLAGS manually.  AM_PATH_XML2 calls
xml2-config --libs and xml2-config --cflags respectively to set these
values.  So just set them to whatever you get when you run these on the
command line.  So basically change the configure.in from this:

AM_PATH_XML2(2.0.0, , AC_MSG_ERROR(libxml2 must be installed.))
LIBS="$LIBS $XML_LIBS" # gcc flags CXXFLAGS="-Wall -fexceptions
-D_XOPEN_SOURCE=500 $XML_CFLAGS"

to this:

#AM_PATH_XML2(2.0.0, , AC_MSG_ERROR(libxml2 must be installed.))
XML_LIBS="whatever you get from xml2-config --libs" XML_CFLAGS="whatever
you get from xml2-config --cflags" LIBS="$LIBS $XML_LIBS" # gcc flags
CXXFLAGS="-Wall -fexceptions -D_XOPEN_SOURCE=500 $XML_CFLAGS"

now run the ./bootstrap script and try building again.  Not ideal but
should get you going until we can figure out what the deal is with your
libxml2.

--oren





                      Justin Pauley

                      <jp...@fs...>        To:
OM...@th...

                                               cc:
qui...@li...,

                      06/12/2002 03:32
qui...@li...

                      PM                       Subject:  RE:
[Quickfix-developers] Version 1.1.0 is available!









[root@eats quickfix]# xml2-config --version
2.4.22
[root@eats quickfix]# xml2-config --cflags -I/usr/local/include/libxml2
[root@eats quickfix]# xml2-config --libs -L/usr/local/lib -lxml2 -lz -lm


Basically, I just did the configure;make;make install

Any ideas?
Justin

-----Original Message-----
From: OM...@th... [mailto:OM...@th...]
Sent: Wednesday, June 12, 2002 1:49 PM
To: jp...@fs...
Cc: qui...@li...;
qui...@li...
Subject: RE: [Quickfix-developers] Version 1.1.0 is available!



Well the second problem you have is probably another symptom of the
first warning you were given.  It looks like it is having difficulty
located your libxml2 package, or at least parts of it.  What is your
output when you type 'xml2-config --version --cflags --libs', the output
should look something like this...

-I/usr/include/libxml2/libxml -I/usr/include/libxml2
-L/usr/lib -lxml2 -lz -lm
2.4.16

Also, how did you install libxml2.  I see it is in local, did you
install with a tar.gz file?  The script doing the checking was written
by the libxml guys so I would imagine it is trying to tell us something
about your installation.

--oren


|---------+----------------------------------------------->
|         |           Justin Pauley <jp...@fs...>     |
|         |           Sent by:                            |
|         |           qui...@li...ur|
|         |           ceforge.net                         |
|         |                                               |
|         |                                               |
|         |           06/12/2002 02:04 PM                 |
|         |                                               |
|---------+----------------------------------------------->

>-----------------------------------------------------------------------
-----------------------|
  |
|
  |       To:       OM...@th...
|
  |       cc:       qui...@li...
|
  |       Subject:  RE: [Quickfix-developers] Version 1.1.0 is
available!                        |

>-----------------------------------------------------------------------
-----------------------|




I am having a problem installing it: I have libxml2 installed however I
get the following error message during a ./configure:

checking for xml2-config... (cached) /usr/local/bin/xml2-config checking
for libxml - version >= 2.0.0... no
*** Could not run libxml test program, checking why...
*** The test program failed to compile or link. See the file config.log
for the
*** exact error that occured. This usually means LIBXML was incorrectly
installed
*** or that you have moved LIBXML since it was installed. In the latter
case, you
*** may want to edit the xml2-config script: /usr/local/bin/xml2-config
configure: error: libxml2 must be installed.

I checked config.log and I saw:
configure:2317: gcc -o conftest -g -O2 -I/usr/local/include/libxml2
conftest.c  -L/usr/local/lib -lxml2 -lz -lm 1>&5
configure:2309:24: xmlversion.h: No such file or directory

I found xmlversion.h in /usr/local/include/libxml2/libxml (default
install directory)

So I ( I know this is bad practice but nothing else worked!) : cp
/usr/local/include/libxml2/libxml/* /usr/local/include/libxml2

Which got rid of the problem during the configure, however, when I did
the make I get:


[root@eats quickfix]# make
cd . && aclocal
aclocal: configure.in: 20: macro `AM_PATH_XML2' not found in library
make: *** [aclocal.m4] Error 1


Any ideas??

And thanks for the upgrade!!

Justin Pauley

-----Original Message-----
From: qui...@li...
[mailto:qui...@li...] On Behalf Of
OM...@th...
Sent: Wednesday, June 12, 2002 10:43 AM
To:  qui...@li...
Subject: [Quickfix-developers] Version 1.1.0 is available!


Version 1.1.0, our first really major release since 1.0.0, is now
available from http://quickfix.thoughtworks.com.

Thank you to everyone who provided feedback, and submitted patches. This
version has major new functionality, bug fixes, more compliance fixes,
and performance enhancements. The release notes are posted below, but
first a couple words for people planning on upgrading.

First of all, this release is most important for people who plan on
doing a lot of throughput and maintain many sessions. The new filestore
is much more efficient memory wise, and the addition of the
ThreadedSocketInitiator and ThreadedSocketAcceptor provide much better
performance and scalability.

When upgrading, please keep in mind the following:

- QuickFIX now uses libxml2.  The folks at libxml has requested all new
projects stop using libxml1 and we are complying with this. You will
need libxml2 installed to build newer versions.

- The signitures for toApp and toAdmin in the Application interface has
changed.  Your applications will need to reflect this change to compile.
The message class is no longer const, this allows you to add fields to a
message before it is sent out.  Ideal for adding additional fields to
messages like Logons and such.

- FileStore has been rewritten.  As a result, the file format has
changed. You should not mix QuickFIX logs from earlier versions with
1.1.0.

- PosDup message are now passed to the application callbacks.  You will
now need to have your application verify whether it wants to process a
particular message that may be a duplicate.

Other than that, here are the release notes.  Please provide everyone
with feedback about this version on this list.

RELEASE NOTES
________________

1.1.0
-----
Added support for messages with repeating groups.

Added ThreadedSocketInitiator and ThreadedSocketAcceptor. Each session
has it own thread for listening on a socket and one for processing
messages.

The signature for toApp and toAdmin have changed from ( const Message&,
const SessionID& ) to ( Message&, const SessionID& ). This allows
applications to add fields to messages before they are sent out.
Particularly useful for administrative messages that need fields that
arn't added by default.

Filestore is much more memory efficient. Only file offsets are stored in
memory and messages are retreived on in as needed basis. This keeps
memory use way down and also is a little faster for normal operations.

On Linux and Solaris upgraded from libxml to libxml2. It is recomended
by the libxml guys that all new applications use libxml2. configure will
verify that libxml is installed on a system and automatically add the
necessary command line parameters.

Possible duplicate messages are now passed to the fromAdmin and fromApp
application callbacks. Applications must now check for this field and
determine how possible duplicate messages should be handled.

Values.h correctly generated enumerations for fields of type INT.

Validation works with STRING enumerations, not just CHAR and INT.

Sockets are now properly closed if a connection fails. This fixes a leak
in socket resources that appeared after a large number of reconnect
attempts.

RefTagID, RefMsgType are no longer added to reject message in versions
of FIX 4.1 and earlier. BusinessMessageReject no longer used in FIX
versions 4.1 and earlier.

Improved DataDictionary generation. More enumerations are listed.

--oren


_______________________________________________________________

Sponsored by:
ThinkGeek at http://www.ThinkGeek.com/
_______________________________________________
Quickfix-developers mailing list
Qui...@li...
https://lists.sourceforge.net/lists/listinfo/quickfix-developers


_______________________________________________________________

Sponsored by:
ThinkGeek at http://www.ThinkGeek.com/
_______________________________________________
Quickfix-developers mailing list
Qui...@li...
https://lists.sourceforge.net/lists/listinfo/quickfix-developers

RE: [Quickfix-developers] Version 1.1.0 is available!

[Justin P. <jp...@fs...>]

Oi! Your suggestion worked and I got it compiled and installed (I only
have libxml2 installed btw and I have
/usr/local/share/aclocal/libxml.m4) 


I no longer have the segfault problem (except when I run tradeclient
without a file (once by mistake)). Now, however, I have a new problem. I
run ordermatch and tradeclient and it connects and tradeclient sends
login and stuff and after I enter an order tradeclient does the: OUT:
8=FIX.4.19=9135=D34=249=direct5752=20020612-23:40:1756=IB11=000021=138=1
040=154=155=rhat59=010=164 and ordermatch does nothing other than
display:
Logout - BeginString: FIX.4.1, SenderCompID: IB, TargetCompID: direct57
Logout - BeginString: FIX.4.1, SenderCompID: IB, TargetCompID: direct57

I checked ordermatches log and I came up with this:
8=FIX.4.19=6135=A34=149=IB52=20020612-23:40:0156=direct5798=0108=3010=14
98=FIX.4.19=8235=334=249=IB52=20020612-23:40:1756=direct5745=258=Unsuppo
rted message type10=141

Any ideas?


Thanks,
Justin

-----Original Message-----
From: OM...@th... [mailto:OM...@th...] 
Sent: Wednesday, June 12, 2002 6:07 PM
To: jp...@fs...
Cc: qui...@li...;
qui...@li...
Subject: RE: [Quickfix-developers] Version 1.1.0 is available!



heh, kind of funny.  libxml does the installation, checks it, and says
the installation is wrong.  Looks kind of like immovable object meets
irresistable force.  I'd like to hear from anyone else who has seen
this.

Do you have libxml and libxml-devel installed, or just libxml? Also
check to see if you have libxml.m4 somewhere on your system.  I just
want to know so I have the information.

In the interim you can probably just disable the script and not worry
about it.  In the confiure.in, comment out the AM_PATH_XML2 call, and
just manually set XML_LIBS and XML_CFLAGS manually.  AM_PATH_XML2 calls
xml2-config --libs and xml2-config --cflags respectively to set these
values.  So just set them to whatever you get when you run these on the
command line.  So basically change the configure.in from this:

AM_PATH_XML2(2.0.0, , AC_MSG_ERROR(libxml2 must be installed.))
LIBS="$LIBS $XML_LIBS" # gcc flags CXXFLAGS="-Wall -fexceptions
-D_XOPEN_SOURCE=500 $XML_CFLAGS"

to this:

#AM_PATH_XML2(2.0.0, , AC_MSG_ERROR(libxml2 must be installed.))
XML_LIBS="whatever you get from xml2-config --libs" XML_CFLAGS="whatever
you get from xml2-config --cflags" LIBS="$LIBS $XML_LIBS" # gcc flags
CXXFLAGS="-Wall -fexceptions -D_XOPEN_SOURCE=500 $XML_CFLAGS"

now run the ./bootstrap script and try building again.  Not ideal but
should get you going until we can figure out what the deal is with your
libxml2.

--oren



 

                      Justin Pauley

                      <jp...@fs...>        To:
OM...@th...

                                               cc:
qui...@li...,

                      06/12/2002 03:32
qui...@li...

                      PM                       Subject:  RE:
[Quickfix-developers] Version 1.1.0 is available!

 

 





[root@eats quickfix]# xml2-config --version
2.4.22
[root@eats quickfix]# xml2-config --cflags -I/usr/local/include/libxml2
[root@eats quickfix]# xml2-config --libs -L/usr/local/lib -lxml2 -lz -lm


Basically, I just did the configure;make;make install

Any ideas?
Justin

-----Original Message-----
From: OM...@th... [mailto:OM...@th...]
Sent: Wednesday, June 12, 2002 1:49 PM
To: jp...@fs...
Cc: qui...@li...;
qui...@li...
Subject: RE: [Quickfix-developers] Version 1.1.0 is available!



Well the second problem you have is probably another symptom of the
first warning you were given.  It looks like it is having difficulty
located your libxml2 package, or at least parts of it.  What is your
output when you type 'xml2-config --version --cflags --libs', the output
should look something like this...

-I/usr/include/libxml2/libxml -I/usr/include/libxml2
-L/usr/lib -lxml2 -lz -lm
2.4.16

Also, how did you install libxml2.  I see it is in local, did you
install with a tar.gz file?  The script doing the checking was written
by the libxml guys so I would imagine it is trying to tell us something
about your installation.

--oren


|---------+----------------------------------------------->
|         |           Justin Pauley <jp...@fs...>     |
|         |           Sent by:                            |
|         |           qui...@li...ur|
|         |           ceforge.net                         |
|         |                                               |
|         |                                               |
|         |           06/12/2002 02:04 PM                 |
|         |                                               |
|---------+----------------------------------------------->

>-----------------------------------------------------------------------
-----------------------|
  |
|
  |       To:       OM...@th...
|
  |       cc:       qui...@li...
|
  |       Subject:  RE: [Quickfix-developers] Version 1.1.0 is
available!                        |

>-----------------------------------------------------------------------
-----------------------|




I am having a problem installing it: I have libxml2 installed however I
get the following error message during a ./configure:

checking for xml2-config... (cached) /usr/local/bin/xml2-config checking
for libxml - version >= 2.0.0... no
*** Could not run libxml test program, checking why...
*** The test program failed to compile or link. See the file config.log
for the
*** exact error that occured. This usually means LIBXML was incorrectly
installed
*** or that you have moved LIBXML since it was installed. In the latter
case, you
*** may want to edit the xml2-config script: /usr/local/bin/xml2-config
configure: error: libxml2 must be installed.

I checked config.log and I saw:
configure:2317: gcc -o conftest -g -O2 -I/usr/local/include/libxml2
conftest.c  -L/usr/local/lib -lxml2 -lz -lm 1>&5
configure:2309:24: xmlversion.h: No such file or directory

I found xmlversion.h in /usr/local/include/libxml2/libxml (default
install directory)

So I ( I know this is bad practice but nothing else worked!) : cp
/usr/local/include/libxml2/libxml/* /usr/local/include/libxml2

Which got rid of the problem during the configure, however, when I did
the make I get:


[root@eats quickfix]# make
cd . && aclocal
aclocal: configure.in: 20: macro `AM_PATH_XML2' not found in library
make: *** [aclocal.m4] Error 1


Any ideas??

And thanks for the upgrade!!

Justin Pauley

-----Original Message-----
From: qui...@li...
[mailto:qui...@li...] On Behalf Of
OM...@th...
Sent: Wednesday, June 12, 2002 10:43 AM
To:  qui...@li...
Subject: [Quickfix-developers] Version 1.1.0 is available!


Version 1.1.0, our first really major release since 1.0.0, is now
available from http://quickfix.thoughtworks.com.

Thank you to everyone who provided feedback, and submitted patches. This
version has major new functionality, bug fixes, more compliance fixes,
and performance enhancements. The release notes are posted below, but
first a couple words for people planning on upgrading.

First of all, this release is most important for people who plan on
doing a lot of throughput and maintain many sessions. The new filestore
is much more efficient memory wise, and the addition of the
ThreadedSocketInitiator and ThreadedSocketAcceptor provide much better
performance and scalability.

When upgrading, please keep in mind the following:

- QuickFIX now uses libxml2.  The folks at libxml has requested all new
projects stop using libxml1 and we are complying with this. You will
need libxml2 installed to build newer versions.

- The signitures for toApp and toAdmin in the Application interface has
changed.  Your applications will need to reflect this change to compile.
The message class is no longer const, this allows you to add fields to a
message before it is sent out.  Ideal for adding additional fields to
messages like Logons and such.

- FileStore has been rewritten.  As a result, the file format has
changed. You should not mix QuickFIX logs from earlier versions with
1.1.0.

- PosDup message are now passed to the application callbacks.  You will
now need to have your application verify whether it wants to process a
particular message that may be a duplicate.

Other than that, here are the release notes.  Please provide everyone
with feedback about this version on this list.

RELEASE NOTES
________________

1.1.0
-----
Added support for messages with repeating groups.

Added ThreadedSocketInitiator and ThreadedSocketAcceptor. Each session
has it own thread for listening on a socket and one for processing
messages.

The signature for toApp and toAdmin have changed from ( const Message&,
const SessionID& ) to ( Message&, const SessionID& ). This allows
applications to add fields to messages before they are sent out.
Particularly useful for administrative messages that need fields that
arn't added by default.

Filestore is much more memory efficient. Only file offsets are stored in
memory and messages are retreived on in as needed basis. This keeps
memory use way down and also is a little faster for normal operations.

On Linux and Solaris upgraded from libxml to libxml2. It is recomended
by the libxml guys that all new applications use libxml2. configure will
verify that libxml is installed on a system and automatically add the
necessary command line parameters.

Possible duplicate messages are now passed to the fromAdmin and fromApp
application callbacks. Applications must now check for this field and
determine how possible duplicate messages should be handled.

Values.h correctly generated enumerations for fields of type INT.

Validation works with STRING enumerations, not just CHAR and INT.

Sockets are now properly closed if a connection fails. This fixes a leak
in socket resources that appeared after a large number of reconnect
attempts.

RefTagID, RefMsgType are no longer added to reject message in versions
of FIX 4.1 and earlier. BusinessMessageReject no longer used in FIX
versions 4.1 and earlier.

Improved DataDictionary generation. More enumerations are listed.

--oren


_______________________________________________________________

Sponsored by:
ThinkGeek at http://www.ThinkGeek.com/
_______________________________________________
Quickfix-developers mailing list
Qui...@li...
https://lists.sourceforge.net/lists/listinfo/quickfix-developers


_______________________________________________________________

Sponsored by:
ThinkGeek at http://www.ThinkGeek.com/
_______________________________________________
Quickfix-developers mailing list
Qui...@li...
https://lists.sourceforge.net/lists/listinfo/quickfix-developers

RE: [Quickfix-developers] Version 1.1.0 is available!

[<OM...@th...>]

heh, kind of funny.  libxml does the installation, checks it, and says the
installation is wrong.  Looks kind of like immovable object meets
irresistable force.  I'd like to hear from anyone else who has seen this.

Do you have libxml and libxml-devel installed, or just libxml? Also check
to see if you have libxml.m4 somewhere on your system.  I just want to know
so I have the information.

In the interim you can probably just disable the script and not worry about
it.  In the confiure.in, comment out the AM_PATH_XML2 call, and just
manually set XML_LIBS and XML_CFLAGS manually.  AM_PATH_XML2 calls
xml2-config --libs and xml2-config --cflags respectively to set these
values.  So just set them to whatever you get when you run these on the
command line.  So basically change the configure.in from this:

AM_PATH_XML2(2.0.0, , AC_MSG_ERROR(libxml2 must be installed.))
LIBS="$LIBS $XML_LIBS"
# gcc flags
CXXFLAGS="-Wall -fexceptions -D_XOPEN_SOURCE=500 $XML_CFLAGS"

to this:

#AM_PATH_XML2(2.0.0, , AC_MSG_ERROR(libxml2 must be installed.))
XML_LIBS="whatever you get from xml2-config --libs"
XML_CFLAGS="whatever you get from xml2-config --cflags"
LIBS="$LIBS $XML_LIBS"
# gcc flags
CXXFLAGS="-Wall -fexceptions -D_XOPEN_SOURCE=500 $XML_CFLAGS"

now run the ./bootstrap script and try building again.  Not ideal but
should get you going until we can figure out what the deal is with your
libxml2.

--oren



                                                                                                                                       
                      Justin Pauley                                                                                                    
                      <jp...@fs...>        To:       OM...@th...                                                      
                                               cc:       qui...@li...,                                    
                      06/12/2002 03:32          qui...@li...                                        
                      PM                       Subject:  RE: [Quickfix-developers] Version 1.1.0 is available!                         
                                                                                                                                       
                                                                                                                                       




[root@eats quickfix]# xml2-config --version
2.4.22
[root@eats quickfix]# xml2-config --cflags
-I/usr/local/include/libxml2
[root@eats quickfix]# xml2-config --libs
-L/usr/local/lib -lxml2 -lz -lm


Basically, I just did the configure;make;make install

Any ideas?
Justin

-----Original Message-----
From: OM...@th... [mailto:OM...@th...]
Sent: Wednesday, June 12, 2002 1:49 PM
To: jp...@fs...
Cc: qui...@li...;
qui...@li...
Subject: RE: [Quickfix-developers] Version 1.1.0 is available!



Well the second problem you have is probably another symptom of the
first warning you were given.  It looks like it is having difficulty
located your libxml2 package, or at least parts of it.  What is your
output when you type 'xml2-config --version --cflags --libs', the output
should look something like this...

-I/usr/include/libxml2/libxml -I/usr/include/libxml2
-L/usr/lib -lxml2 -lz -lm
2.4.16

Also, how did you install libxml2.  I see it is in local, did you
install with a tar.gz file?  The script doing the checking was written
by the libxml guys so I would imagine it is trying to tell us something
about your installation.

--oren


|---------+----------------------------------------------->
|         |           Justin Pauley <jp...@fs...>     |
|         |           Sent by:                            |
|         |           qui...@li...ur|
|         |           ceforge.net                         |
|         |                                               |
|         |                                               |
|         |           06/12/2002 02:04 PM                 |
|         |                                               |
|---------+----------------------------------------------->

>-----------------------------------------------------------------------
-----------------------|
  |
|
  |       To:       OM...@th...
|
  |       cc:       qui...@li...
|
  |       Subject:  RE: [Quickfix-developers] Version 1.1.0 is
available!                        |

>-----------------------------------------------------------------------
-----------------------|




I am having a problem installing it: I have libxml2 installed however I
get the following error message during a ./configure:

checking for xml2-config... (cached) /usr/local/bin/xml2-config checking
for libxml - version >= 2.0.0... no
*** Could not run libxml test program, checking why...
*** The test program failed to compile or link. See the file config.log
for the
*** exact error that occured. This usually means LIBXML was incorrectly
installed
*** or that you have moved LIBXML since it was installed. In the latter
case, you
*** may want to edit the xml2-config script: /usr/local/bin/xml2-config
configure: error: libxml2 must be installed.

I checked config.log and I saw:
configure:2317: gcc -o conftest -g -O2 -I/usr/local/include/libxml2
conftest.c  -L/usr/local/lib -lxml2 -lz -lm 1>&5
configure:2309:24: xmlversion.h: No such file or directory

I found xmlversion.h in /usr/local/include/libxml2/libxml (default
install directory)

So I ( I know this is bad practice but nothing else worked!) : cp
/usr/local/include/libxml2/libxml/* /usr/local/include/libxml2

Which got rid of the problem during the configure, however, when I did
the make I get:


[root@eats quickfix]# make
cd . && aclocal
aclocal: configure.in: 20: macro `AM_PATH_XML2' not found in library
make: *** [aclocal.m4] Error 1


Any ideas??

And thanks for the upgrade!!

Justin Pauley

-----Original Message-----
From: qui...@li...
[mailto:qui...@li...] On Behalf Of
OM...@th...
Sent: Wednesday, June 12, 2002 10:43 AM
To:  qui...@li...
Subject: [Quickfix-developers] Version 1.1.0 is available!


Version 1.1.0, our first really major release since 1.0.0, is now
available from http://quickfix.thoughtworks.com.

Thank you to everyone who provided feedback, and submitted patches. This
version has major new functionality, bug fixes, more compliance fixes,
and performance enhancements. The release notes are posted below, but
first a couple words for people planning on upgrading.

First of all, this release is most important for people who plan on
doing a lot of throughput and maintain many sessions. The new filestore
is much more efficient memory wise, and the addition of the
ThreadedSocketInitiator and ThreadedSocketAcceptor provide much better
performance and scalability.

When upgrading, please keep in mind the following:

- QuickFIX now uses libxml2.  The folks at libxml has requested all new
projects stop using libxml1 and we are complying with this. You will
need libxml2 installed to build newer versions.

- The signitures for toApp and toAdmin in the Application interface has
changed.  Your applications will need to reflect this change to compile.
The message class is no longer const, this allows you to add fields to a
message before it is sent out.  Ideal for adding additional fields to
messages like Logons and such.

- FileStore has been rewritten.  As a result, the file format has
changed. You should not mix QuickFIX logs from earlier versions with
1.1.0.

- PosDup message are now passed to the application callbacks.  You will
now need to have your application verify whether it wants to process a
particular message that may be a duplicate.

Other than that, here are the release notes.  Please provide everyone
with feedback about this version on this list.

RELEASE NOTES
________________

1.1.0
-----
Added support for messages with repeating groups.

Added ThreadedSocketInitiator and ThreadedSocketAcceptor. Each session
has it own thread for listening on a socket and one for processing
messages.

The signature for toApp and toAdmin have changed from ( const Message&,
const SessionID& ) to ( Message&, const SessionID& ). This allows
applications to add fields to messages before they are sent out.
Particularly useful for administrative messages that need fields that
arn't added by default.

Filestore is much more memory efficient. Only file offsets are stored in
memory and messages are retreived on in as needed basis. This keeps
memory use way down and also is a little faster for normal operations.

On Linux and Solaris upgraded from libxml to libxml2. It is recomended
by the libxml guys that all new applications use libxml2. configure will
verify that libxml is installed on a system and automatically add the
necessary command line parameters.

Possible duplicate messages are now passed to the fromAdmin and fromApp
application callbacks. Applications must now check for this field and
determine how possible duplicate messages should be handled.

Values.h correctly generated enumerations for fields of type INT.

Validation works with STRING enumerations, not just CHAR and INT.

Sockets are now properly closed if a connection fails. This fixes a leak
in socket resources that appeared after a large number of reconnect
attempts.

RefTagID, RefMsgType are no longer added to reject message in versions
of FIX 4.1 and earlier. BusinessMessageReject no longer used in FIX
versions 4.1 and earlier.

Improved DataDictionary generation. More enumerations are listed.

--oren


_______________________________________________________________

Sponsored by:
ThinkGeek at http://www.ThinkGeek.com/
_______________________________________________
Quickfix-developers mailing list
Qui...@li...
https://lists.sourceforge.net/lists/listinfo/quickfix-developers


_______________________________________________________________

Sponsored by:
ThinkGeek at http://www.ThinkGeek.com/
_______________________________________________
Quickfix-developers mailing list
Qui...@li...
https://lists.sourceforge.net/lists/listinfo/quickfix-developers

RE: [Quickfix-developers] Version 1.1.0 is available!

[Justin P. <jp...@fs...>]

[root@eats quickfix]# xml2-config --version                
2.4.22
[root@eats quickfix]# xml2-config --cflags 
-I/usr/local/include/libxml2
[root@eats quickfix]# xml2-config --libs  
-L/usr/local/lib -lxml2 -lz -lm


Basically, I just did the configure;make;make install

Any ideas?
Justin

-----Original Message-----
From: OM...@th... [mailto:OM...@th...] 
Sent: Wednesday, June 12, 2002 1:49 PM
To: jp...@fs...
Cc: qui...@li...;
qui...@li...
Subject: RE: [Quickfix-developers] Version 1.1.0 is available!



Well the second problem you have is probably another symptom of the
first warning you were given.  It looks like it is having difficulty
located your libxml2 package, or at least parts of it.  What is your
output when you type 'xml2-config --version --cflags --libs', the output
should look something like this...

-I/usr/include/libxml2/libxml -I/usr/include/libxml2
-L/usr/lib -lxml2 -lz -lm
2.4.16

Also, how did you install libxml2.  I see it is in local, did you
install with a tar.gz file?  The script doing the checking was written
by the libxml guys so I would imagine it is trying to tell us something
about your installation.

--oren


|---------+----------------------------------------------->
|         |           Justin Pauley <jp...@fs...>     |
|         |           Sent by:                            |
|         |           qui...@li...ur|
|         |           ceforge.net                         |
|         |                                               |
|         |                                               |
|         |           06/12/2002 02:04 PM                 |
|         |                                               |
|---------+----------------------------------------------->
 
>-----------------------------------------------------------------------
-----------------------|
  |
|
  |       To:       OM...@th...
|
  |       cc:       qui...@li...
|
  |       Subject:  RE: [Quickfix-developers] Version 1.1.0 is
available!                        |
 
>-----------------------------------------------------------------------
-----------------------|




I am having a problem installing it: I have libxml2 installed however I
get the following error message during a ./configure:

checking for xml2-config... (cached) /usr/local/bin/xml2-config checking
for libxml - version >= 2.0.0... no
*** Could not run libxml test program, checking why...
*** The test program failed to compile or link. See the file config.log
for the
*** exact error that occured. This usually means LIBXML was incorrectly
installed
*** or that you have moved LIBXML since it was installed. In the latter
case, you
*** may want to edit the xml2-config script: /usr/local/bin/xml2-config
configure: error: libxml2 must be installed.

I checked config.log and I saw:
configure:2317: gcc -o conftest -g -O2 -I/usr/local/include/libxml2
conftest.c  -L/usr/local/lib -lxml2 -lz -lm 1>&5
configure:2309:24: xmlversion.h: No such file or directory

I found xmlversion.h in /usr/local/include/libxml2/libxml (default
install directory)

So I ( I know this is bad practice but nothing else worked!) : cp
/usr/local/include/libxml2/libxml/* /usr/local/include/libxml2

Which got rid of the problem during the configure, however, when I did
the make I get:


[root@eats quickfix]# make
cd . && aclocal
aclocal: configure.in: 20: macro `AM_PATH_XML2' not found in library
make: *** [aclocal.m4] Error 1


Any ideas??

And thanks for the upgrade!!

Justin Pauley

-----Original Message-----
From: qui...@li...
[mailto:qui...@li...] On Behalf Of
OM...@th...
Sent: Wednesday, June 12, 2002 10:43 AM
To:  qui...@li...
Subject: [Quickfix-developers] Version 1.1.0 is available!


Version 1.1.0, our first really major release since 1.0.0, is now
available from http://quickfix.thoughtworks.com.

Thank you to everyone who provided feedback, and submitted patches. This
version has major new functionality, bug fixes, more compliance fixes,
and performance enhancements. The release notes are posted below, but
first a couple words for people planning on upgrading.

First of all, this release is most important for people who plan on
doing a lot of throughput and maintain many sessions. The new filestore
is much more efficient memory wise, and the addition of the
ThreadedSocketInitiator and ThreadedSocketAcceptor provide much better
performance and scalability.

When upgrading, please keep in mind the following:

- QuickFIX now uses libxml2.  The folks at libxml has requested all new
projects stop using libxml1 and we are complying with this. You will
need libxml2 installed to build newer versions.

- The signitures for toApp and toAdmin in the Application interface has
changed.  Your applications will need to reflect this change to compile.
The message class is no longer const, this allows you to add fields to a
message before it is sent out.  Ideal for adding additional fields to
messages like Logons and such.

- FileStore has been rewritten.  As a result, the file format has
changed. You should not mix QuickFIX logs from earlier versions with
1.1.0.

- PosDup message are now passed to the application callbacks.  You will
now need to have your application verify whether it wants to process a
particular message that may be a duplicate.

Other than that, here are the release notes.  Please provide everyone
with feedback about this version on this list.

RELEASE NOTES
________________

1.1.0
-----
Added support for messages with repeating groups.

Added ThreadedSocketInitiator and ThreadedSocketAcceptor. Each session
has it own thread for listening on a socket and one for processing
messages.

The signature for toApp and toAdmin have changed from ( const Message&,
const SessionID& ) to ( Message&, const SessionID& ). This allows
applications to add fields to messages before they are sent out.
Particularly useful for administrative messages that need fields that
arn't added by default.

Filestore is much more memory efficient. Only file offsets are stored in
memory and messages are retreived on in as needed basis. This keeps
memory use way down and also is a little faster for normal operations.

On Linux and Solaris upgraded from libxml to libxml2. It is recomended
by the libxml guys that all new applications use libxml2. configure will
verify that libxml is installed on a system and automatically add the
necessary command line parameters.

Possible duplicate messages are now passed to the fromAdmin and fromApp
application callbacks. Applications must now check for this field and
determine how possible duplicate messages should be handled.

Values.h correctly generated enumerations for fields of type INT.

Validation works with STRING enumerations, not just CHAR and INT.

Sockets are now properly closed if a connection fails. This fixes a leak
in socket resources that appeared after a large number of reconnect
attempts.

RefTagID, RefMsgType are no longer added to reject message in versions
of FIX 4.1 and earlier. BusinessMessageReject no longer used in FIX
versions 4.1 and earlier.

Improved DataDictionary generation. More enumerations are listed.

--oren


_______________________________________________________________

Sponsored by:
ThinkGeek at http://www.ThinkGeek.com/
_______________________________________________
Quickfix-developers mailing list
Qui...@li...
https://lists.sourceforge.net/lists/listinfo/quickfix-developers


_______________________________________________________________

Sponsored by:
ThinkGeek at http://www.ThinkGeek.com/
_______________________________________________
Quickfix-developers mailing list
Qui...@li...
https://lists.sourceforge.net/lists/listinfo/quickfix-developers

RE: [Quickfix-developers] Version 1.1.0 is available!

[<OM...@th...>]

Well the second problem you have is probably another symptom of the first
warning you were given.  It looks like it is having difficulty located your
libxml2 package, or at least parts of it.  What is your output when you
type 'xml2-config --version --cflags --libs', the output should look
something like this...

-I/usr/include/libxml2/libxml -I/usr/include/libxml2
-L/usr/lib -lxml2 -lz -lm
2.4.16

Also, how did you install libxml2.  I see it is in local, did you install
with a tar.gz file?  The script doing the checking was written by the
libxml guys so I would imagine it is trying to tell us something about your
installation.

--oren


|---------+----------------------------------------------->
|         |           Justin Pauley <jp...@fs...>     |
|         |           Sent by:                            |
|         |           qui...@li...ur|
|         |           ceforge.net                         |
|         |                                               |
|         |                                               |
|         |           06/12/2002 02:04 PM                 |
|         |                                               |
|---------+----------------------------------------------->
  >----------------------------------------------------------------------------------------------|
  |                                                                                              |
  |       To:       OM...@th...                                                     |
  |       cc:       qui...@li...                                    |
  |       Subject:  RE: [Quickfix-developers] Version 1.1.0 is available!                        |
  >----------------------------------------------------------------------------------------------|




I am having a problem installing it: I have libxml2 installed however I
get the following error message during a ./configure:

checking for xml2-config... (cached) /usr/local/bin/xml2-config
checking for libxml - version >= 2.0.0... no
*** Could not run libxml test program, checking why...
*** The test program failed to compile or link. See the file config.log
for the
*** exact error that occured. This usually means LIBXML was incorrectly
installed
*** or that you have moved LIBXML since it was installed. In the latter
case, you
*** may want to edit the xml2-config script: /usr/local/bin/xml2-config
configure: error: libxml2 must be installed.

I checked config.log and I saw:
configure:2317: gcc -o conftest -g -O2 -I/usr/local/include/libxml2
conftest.c  -L/usr/local/lib -lxml2 -lz -lm 1>&5
configure:2309:24: xmlversion.h: No such file or directory

I found xmlversion.h in /usr/local/include/libxml2/libxml (default
install directory)

So I ( I know this is bad practice but nothing else worked!) : cp
/usr/local/include/libxml2/libxml/* /usr/local/include/libxml2

Which got rid of the problem during the configure, however, when I did
the make I get:


[root@eats quickfix]# make
cd . && aclocal
aclocal: configure.in: 20: macro `AM_PATH_XML2' not found in library
make: *** [aclocal.m4] Error 1


Any ideas??

And thanks for the upgrade!!

Justin Pauley

-----Original Message-----
From: qui...@li...
[mailto:qui...@li...] On Behalf Of
OM...@th...
Sent: Wednesday, June 12, 2002 10:43 AM
To:  qui...@li...
Subject: [Quickfix-developers] Version 1.1.0 is available!


Version 1.1.0, our first really major release since 1.0.0, is now
available from http://quickfix.thoughtworks.com.

Thank you to everyone who provided feedback, and submitted patches. This
version has major new functionality, bug fixes, more compliance fixes,
and performance enhancements. The release notes are posted below, but
first a couple words for people planning on upgrading.

First of all, this release is most important for people who plan on
doing a lot of throughput and maintain many sessions. The new filestore
is much more efficient memory wise, and the addition of the
ThreadedSocketInitiator and ThreadedSocketAcceptor provide much better
performance and scalability.

When upgrading, please keep in mind the following:

- QuickFIX now uses libxml2.  The folks at libxml has requested all new
projects stop using libxml1 and we are complying with this. You will
need libxml2 installed to build newer versions.

- The signitures for toApp and toAdmin in the Application interface has
changed.  Your applications will need to reflect this change to compile.
The message class is no longer const, this allows you to add fields to a
message before it is sent out.  Ideal for adding additional fields to
messages like Logons and such.

- FileStore has been rewritten.  As a result, the file format has
changed. You should not mix QuickFIX logs from earlier versions with
1.1.0.

- PosDup message are now passed to the application callbacks.  You will
now need to have your application verify whether it wants to process a
particular message that may be a duplicate.

Other than that, here are the release notes.  Please provide everyone
with feedback about this version on this list.

RELEASE NOTES
________________

1.1.0
-----
Added support for messages with repeating groups.

Added ThreadedSocketInitiator and ThreadedSocketAcceptor. Each session
has it own thread for listening on a socket and one for processing
messages.

The signature for toApp and toAdmin have changed from ( const Message&,
const SessionID& ) to ( Message&, const SessionID& ). This allows
applications to add fields to messages before they are sent out.
Particularly useful for administrative messages that need fields that
arn't added by default.

Filestore is much more memory efficient. Only file offsets are stored in
memory and messages are retreived on in as needed basis. This keeps
memory use way down and also is a little faster for normal operations.

On Linux and Solaris upgraded from libxml to libxml2. It is recomended
by the libxml guys that all new applications use libxml2. configure will
verify that libxml is installed on a system and automatically add the
necessary command line parameters.

Possible duplicate messages are now passed to the fromAdmin and fromApp
application callbacks. Applications must now check for this field and
determine how possible duplicate messages should be handled.

Values.h correctly generated enumerations for fields of type INT.

Validation works with STRING enumerations, not just CHAR and INT.

Sockets are now properly closed if a connection fails. This fixes a leak
in socket resources that appeared after a large number of reconnect
attempts.

RefTagID, RefMsgType are no longer added to reject message in versions
of FIX 4.1 and earlier. BusinessMessageReject no longer used in FIX
versions 4.1 and earlier.

Improved DataDictionary generation. More enumerations are listed.

--oren


_______________________________________________________________

Sponsored by:
ThinkGeek at http://www.ThinkGeek.com/
_______________________________________________
Quickfix-developers mailing list
Qui...@li...
https://lists.sourceforge.net/lists/listinfo/quickfix-developers


_______________________________________________________________

Sponsored by:
ThinkGeek at http://www.ThinkGeek.com/
_______________________________________________
Quickfix-developers mailing list
Qui...@li...
https://lists.sourceforge.net/lists/listinfo/quickfix-developers

RE: [Quickfix-developers] Version 1.1.0 is available!

[Justin P. <jp...@fs...>]

I am having a problem installing it: I have libxml2 installed however I
get the following error message during a ./configure:

checking for xml2-config... (cached) /usr/local/bin/xml2-config
checking for libxml - version >= 2.0.0... no
*** Could not run libxml test program, checking why...
*** The test program failed to compile or link. See the file config.log
for the
*** exact error that occured. This usually means LIBXML was incorrectly
installed
*** or that you have moved LIBXML since it was installed. In the latter
case, you
*** may want to edit the xml2-config script: /usr/local/bin/xml2-config
configure: error: libxml2 must be installed.

I checked config.log and I saw:
configure:2317: gcc -o conftest -g -O2 -I/usr/local/include/libxml2
conftest.c  -L/usr/local/lib -lxml2 -lz -lm 1>&5
configure:2309:24: xmlversion.h: No such file or directory

I found xmlversion.h in /usr/local/include/libxml2/libxml (default
install directory)

So I ( I know this is bad practice but nothing else worked!) : cp
/usr/local/include/libxml2/libxml/* /usr/local/include/libxml2 

Which got rid of the problem during the configure, however, when I did
the make I get:


[root@eats quickfix]# make
cd . && aclocal
aclocal: configure.in: 20: macro `AM_PATH_XML2' not found in library
make: *** [aclocal.m4] Error 1


Any ideas??

And thanks for the upgrade!!

Justin Pauley

-----Original Message-----
From: qui...@li...
[mailto:qui...@li...] On Behalf Of
OM...@th...
Sent: Wednesday, June 12, 2002 10:43 AM
To:  qui...@li...
Subject: [Quickfix-developers] Version 1.1.0 is available!


Version 1.1.0, our first really major release since 1.0.0, is now
available from http://quickfix.thoughtworks.com.

Thank you to everyone who provided feedback, and submitted patches. This
version has major new functionality, bug fixes, more compliance fixes,
and performance enhancements. The release notes are posted below, but
first a couple words for people planning on upgrading.

First of all, this release is most important for people who plan on
doing a lot of throughput and maintain many sessions. The new filestore
is much more efficient memory wise, and the addition of the
ThreadedSocketInitiator and ThreadedSocketAcceptor provide much better
performance and scalability.

When upgrading, please keep in mind the following:

- QuickFIX now uses libxml2.  The folks at libxml has requested all new
projects stop using libxml1 and we are complying with this. You will
need libxml2 installed to build newer versions.

- The signitures for toApp and toAdmin in the Application interface has
changed.  Your applications will need to reflect this change to compile.
The message class is no longer const, this allows you to add fields to a
message before it is sent out.  Ideal for adding additional fields to
messages like Logons and such.

- FileStore has been rewritten.  As a result, the file format has
changed. You should not mix QuickFIX logs from earlier versions with
1.1.0.

- PosDup message are now passed to the application callbacks.  You will
now need to have your application verify whether it wants to process a
particular message that may be a duplicate.

Other than that, here are the release notes.  Please provide everyone
with feedback about this version on this list.

RELEASE NOTES
________________

1.1.0
-----
Added support for messages with repeating groups.

Added ThreadedSocketInitiator and ThreadedSocketAcceptor. Each session
has it own thread for listening on a socket and one for processing
messages.

The signature for toApp and toAdmin have changed from ( const Message&,
const SessionID& ) to ( Message&, const SessionID& ). This allows
applications to add fields to messages before they are sent out.
Particularly useful for administrative messages that need fields that
arn't added by default.

Filestore is much more memory efficient. Only file offsets are stored in
memory and messages are retreived on in as needed basis. This keeps
memory use way down and also is a little faster for normal operations.

On Linux and Solaris upgraded from libxml to libxml2. It is recomended
by the libxml guys that all new applications use libxml2. configure will
verify that libxml is installed on a system and automatically add the
necessary command line parameters.

Possible duplicate messages are now passed to the fromAdmin and fromApp
application callbacks. Applications must now check for this field and
determine how possible duplicate messages should be handled.

Values.h correctly generated enumerations for fields of type INT.

Validation works with STRING enumerations, not just CHAR and INT.

Sockets are now properly closed if a connection fails. This fixes a leak
in socket resources that appeared after a large number of reconnect
attempts.

RefTagID, RefMsgType are no longer added to reject message in versions
of FIX 4.1 and earlier. BusinessMessageReject no longer used in FIX
versions 4.1 and earlier.

Improved DataDictionary generation. More enumerations are listed.

--oren


_______________________________________________________________

Sponsored by:
ThinkGeek at http://www.ThinkGeek.com/
_______________________________________________
Quickfix-developers mailing list
Qui...@li...
https://lists.sourceforge.net/lists/listinfo/quickfix-developers

[Quickfix-developers] Version 1.1.0 is available!

[<OM...@th...>]

Version 1.1.0, our first really major release since 1.0.0, is now available
from http://quickfix.thoughtworks.com.

Thank you to everyone who provided feedback, and submitted patches. This
version has major new functionality, bug fixes, more compliance fixes, and
performance enhancements. The release notes are posted below, but first a
couple words for people planning on upgrading.

First of all, this release is most important for people who plan on doing a
lot of throughput and maintain many sessions. The new filestore is much
more efficient memory wise, and the addition of the ThreadedSocketInitiator
and ThreadedSocketAcceptor provide much better performance and scalability.

When upgrading, please keep in mind the following:

- QuickFIX now uses libxml2.  The folks at libxml has requested all new
projects stop using libxml1 and we are complying with this. You will need
libxml2 installed to build newer versions.

- The signitures for toApp and toAdmin in the Application interface has
changed.  Your applications will need to reflect this change to compile.
The message class is no longer const, this allows you to add fields to a
message before it is sent out.  Ideal for adding additional fields to
messages like Logons and such.

- FileStore has been rewritten.  As a result, the file format has changed.
You should not mix QuickFIX logs from earlier versions with 1.1.0.

- PosDup message are now passed to the application callbacks.  You will now
need to have your application verify whether it wants to process a
particular message that may be a duplicate.

Other than that, here are the release notes.  Please provide everyone with
feedback about this version on this list.

RELEASE NOTES
________________

1.1.0
-----
Added support for messages with repeating groups.

Added ThreadedSocketInitiator and ThreadedSocketAcceptor. Each session has
it own thread
for listening on a socket and one for processing messages.

The signature for toApp and toAdmin have changed from ( const Message&,
const SessionID& )
to ( Message&, const SessionID& ). This allows applications to add fields
to messages before
they are sent out. Particularly useful for administrative messages that
need fields that arn't
added by default.

Filestore is much more memory efficient. Only file offsets are stored in
memory
and messages are retreived on in as needed basis. This keeps memory use way
down and also is a little faster for normal operations.

On Linux and Solaris upgraded from libxml to libxml2. It is recomended by
the libxml guys that all new applications use libxml2. configure will
verify
that libxml is installed on a system and automatically add the necessary
command line parameters.

Possible duplicate messages are now passed to the fromAdmin and fromApp
application
callbacks. Applications must now check for this field and determine how
possible
duplicate messages should be handled.

Values.h correctly generated enumerations for fields of type INT.

Validation works with STRING enumerations, not just CHAR and INT.

Sockets are now properly closed if a connection fails. This fixes a leak in
socket
resources that appeared after a large number of reconnect attempts.

RefTagID, RefMsgType are no longer added to reject message in versions of
FIX 4.1
and earlier. BusinessMessageReject no longer used in FIX versions 4.1 and
earlier.

Improved DataDictionary generation. More enumerations are listed.

--oren

[Quickfix-developers] Agree with Rainer

[Bernard S. <bsp...@gx...>]

Oren,

	I just want to add my 2 cents worth to Rainer's comment:  This FIX
implementation is exactly what we need.  Once I got through the setup and
configuration issues, I was able to get my FIX implementation up and running
and into test in about 3 weeks.  This has saved me time (or money or both)
and the hassle of dealing with another vendor.  Making this open source was
a great idea!  Looking forward to the next release.

	- Bernard

-----Original Message-----
From: qui...@li...
[mailto:qui...@li...]On Behalf Of
Rainer Staringer
Sent: Monday, June 10, 2002 4:32 AM
To: OM...@th...
Cc: qui...@li...
Subject: Re: [Quickfix-developers] Too many open files



On Friday, June 7, 2002, at 04:16 PM, OM...@th... wrote:

>
> Rainer,
>
> First off, good catch on the file descriptors leak.  One additional
> thing
> you should do is use the socket_close method defined in Utility.h.
> Reason
> is that this function is portable (Windows does not use close on socket
> descriptors. go figure).
>
> Second, just so you know, the new version being released soon has an
> additional multithreaded implementation of the socket code.  In this
> scenario, each session has it's own thread which not only solves the
> connect problem, it also makes it so sessions that take up a lot of
> processing time (if there are database accesses or whatever when an
> application message is processed) do not interfere with other sessions.
> The
> single threaded code should still be updated for the reason you pointed
> out, but you will also have another alternative.  Thanks!

Oren,

That's good news! My application callbacks will probably just queue the
messages and forward them to the main thread, but multiple threads are
of course the cleanest solution for multiple FIX sessions.

Can you give me a rough estimate when the new version will be out?

Another thing I noticed: The problem reported by Bernard (4.2 tags being
sent to a 4.0 partner) is pervasive throughout the Session class. I
wonder if it would not be cleaner to implement 4.0/4.1/4.2 behaviour in
separate Session subclasses, or "strategy" helper objects?

Thanks for making this an open source project! Unlike many other open
source efforts, quickfix is exactly what the world needed... :-)

Rainer



_______________________________________________________________

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -
http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink

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

[Quickfix-developers] release....

[<OM...@th...>]

Sorry for the delay on the release guys, but there was a really weird bug
on the Solaris port that was driving me nuts.  Random bits of memory were
being set to zero for no apparent reason causing all sorts of wacky seg
faults.  I finally played a hunch completely out of nowhere, that turned
out to be right.  Apparently the use of the nanosecond system call was
doing it. Has anyone ever encountered anything like this?  For now I am
using the sleep call instead and the problem is gone.

In any case now that this is fixed I should be able to put the release up
tonight.  I will follow up with another announcement and release notes when
it is available.

--oren

Re: [Quickfix-developers] Too many open files

[Rainer S. <ra...@aa...>]

>
> Do you still have a copy of that 4.2 SequenceReset message? If so can 
> you
> post it here.  It would probably be the best starting point for 
> writing a
> test.  We do have tests with sequence resets so it would be nice to see 
> if
> there is something different or special about this message.
>
> --oren
>

Voila, I undid the change and reproduced the problem:

The following SequenceReset mesage results in a FieldsOutOfOrder 
exception:

8=FIX.4.29=6135=434=32643=Y49=MBT52=20020610-17:53:5056=EURO136=32710=001

Resulting in the following reject message:

ADMIN OUT: 
8=FIX.4.29=9335=334=34249=EURO152=20020610-17:53:5156=MBT45=32658=Incorrect 
Message Structure372=410=061

Maybe the PossDupFlag is the problem?


Just noticed another problem: When talking to the ordermatch example, 
when one stops the ordermatch process with ^Z for a while, exits and 
restarts the client process, continues the server with fg (the previous 
actions in any order...), it is possible to get all manner of wierd 
behaviour, e.g. last time I got an infinite loop of

ADMIN IN: 
8=FIX.4.29=10335=334=161249=TEST52=20020610-17:37:0956=EURO145=159558=Required 
tag missing371=122372=4373=110=227

ADMIN OUT: 
8=FIX.4.29=10335=334=163049=EURO152=20020610-17:37:0956=TEST45=161158=Required 
tag missing371=122372=4373=110=216

ADMIN OUT: 
8=FIX.4.29=6635=234=163149=EURO152=20020610-17:37:0956=TEST7=161316=162910=
013

ADMIN IN: 
8=FIX.4.29=6635=234=163149=TEST52=20020610-17:37:0956=EURO17=161516=162910=
015

ADMIN OUT: 
8=FIX.4.29=7035=434=161543=Y49=EURO152=20020610-17:37:0956=TEST36=1630123=
Y10=241

(EURO1 is the client, TEST is the ordermatch server, this output is from 
the client, continues ad infinitum)

-Rainer

Re: [Quickfix-developers] Too many open files

[<OM...@th...>]

Do you still have a copy of that 4.2 SequenceReset message? If so can you
post it here.  It would probably be the best starting point for writing a
test.  We do have tests with sequence resets so it would be nice to see if
there is something different or special about this message.

--oren



                                                                                                                                       
                      Rainer Staringer                                                                                                 
                      <rainer@aaa-plus.        To:       OM...@th...                                                      
                      com>                     cc:       qui...@li...                                     
                                               Subject:  Re: [Quickfix-developers] Too many open files                                 
                      06/10/2002 10:35                                                                                                 
                      AM                                                                                                               
                                                                                                                                       
                                                                                                                                       





> I expect the new versions will be released either today or tommorow, so
> very soon.  The release number will be 1.1.0.  An anouncement with
> release
> note will be posted here when it is available.

Great!

> I believe the bug reported by Bernard has also been fixed in this
> release
> (extra tags in reject message).  So far that one place is the only
> area I
> am aware of that extra tags were added where they don't belong.  Do you
> know of any more like it?

The RefMsgType tag is also erroneously added in Session::generateReject
( const Message& message, const std::string& str )

Also, Session::generateBusinessReject( const Message& message, int err )
should default to generateReject(message, "Unsupported message type") in
the 4.0/4.1 cases, since the business reject message type is a 4.2
addition.

I checked only the reject messages for now, there might be other
messages with this problem.

Another thing I noticed:

For some reason the structure validating code in Message.h set
m_validStructure to false for a perfectly valid (to my eyes) FIX4.2
SequenceReset message, so I had to comment out some checks in bool
setString ( const std::string& string ) to get things going. I could not
identify the problem from looking at the code, though... Might be worth
adding a test case with a 4.2 SequenceReset.

Rainer

Re: [Quickfix-developers] Too many open files

[Rainer S. <ra...@aa...>]

> I expect the new versions will be released either today or tommorow, so
> very soon.  The release number will be 1.1.0.  An anouncement with 
> release
> note will be posted here when it is available.

Great!

> I believe the bug reported by Bernard has also been fixed in this 
> release
> (extra tags in reject message).  So far that one place is the only 
> area I
> am aware of that extra tags were added where they don't belong.  Do you
> know of any more like it?

The RefMsgType tag is also erroneously added in Session::generateReject
( const Message& message, const std::string& str )

Also, Session::generateBusinessReject( const Message& message, int err ) 
should default to generateReject(message, "Unsupported message type") in 
the 4.0/4.1 cases, since the business reject message type is a 4.2 
addition.

I checked only the reject messages for now, there might be other 
messages with this problem.

Another thing I noticed:

For some reason the structure validating code in Message.h set 
m_validStructure to false for a perfectly valid (to my eyes) FIX4.2 
SequenceReset message, so I had to comment out some checks in bool 
setString ( const std::string& string ) to get things going. I could not 
identify the problem from looking at the code, though... Might be worth 
adding a test case with a 4.2 SequenceReset.

Rainer

Re: [Quickfix-developers] Too many open files

[<OM...@th...>]

Rainer,

I expect the new versions will be released either today or tommorow, so
very soon.  The release number will be 1.1.0.  An anouncement with release
note will be posted here when it is available.

I believe the bug reported by Bernard has also been fixed in this release
(extra tags in reject message).  So far that one place is the only area I
am aware of that extra tags were added where they don't belong.  Do you
know of any more like it?

Right now the one session solution seems to be manageable, however as new
versions are added the differences may start to grow (and you may have more
to report).  A strategy sounds like a good idea for deciding what version
specific fields should be added to a message after the basic message is
constructed.  If new versions start to introduce changes in session logic
(I believe all 4.x versions are the same logic wise), some subclassing may
make sense as well.  Maybe one of us can play around with it.

Most of our tests are written in FIX 4.2 as well.  We are really lacking
coverage with FIX 4.0 and 4.1 tests.  I think we were relying too much on
their similarities to 4.2.  We need to go through the acceptance tests and
write 4.0 and 4.1 versions so all of these little nuances get caught
earlier.

Thanks for the praise and your feedback.

--oren



                                                                                                                                       
                      Rainer Staringer                                                                                                 
                      <rainer@aaa-plus.        To:       OM...@th...                                                      
                      com>                     cc:       qui...@li...                                     
                                               Subject:  Re: [Quickfix-developers] Too many open files                                 
                      06/10/2002 03:31                                                                                                 
                      AM                                                                                                               
                                                                                                                                       
                                                                                                                                       





On Friday, June 7, 2002, at 04:16 PM, OM...@th... wrote:

>
> Rainer,
>
> First off, good catch on the file descriptors leak.  One additional
> thing
> you should do is use the socket_close method defined in Utility.h.
> Reason
> is that this function is portable (Windows does not use close on socket
> descriptors. go figure).
>
> Second, just so you know, the new version being released soon has an
> additional multithreaded implementation of the socket code.  In this
> scenario, each session has it's own thread which not only solves the
> connect problem, it also makes it so sessions that take up a lot of
> processing time (if there are database accesses or whatever when an
> application message is processed) do not interfere with other sessions.
> The
> single threaded code should still be updated for the reason you pointed
> out, but you will also have another alternative.  Thanks!

Oren,

That's good news! My application callbacks will probably just queue the
messages and forward them to the main thread, but multiple threads are
of course the cleanest solution for multiple FIX sessions.

Can you give me a rough estimate when the new version will be out?

Another thing I noticed: The problem reported by Bernard (4.2 tags being
sent to a 4.0 partner) is pervasive throughout the Session class. I
wonder if it would not be cleaner to implement 4.0/4.1/4.2 behaviour in
separate Session subclasses, or "strategy" helper objects?

Thanks for making this an open source project! Unlike many other open
source efforts, quickfix is exactly what the world needed... :-)

Rainer

Re: [Quickfix-developers] Too many open files

[Rainer S. <ra...@aa...>]

On Friday, June 7, 2002, at 04:16 PM, OM...@th... wrote:

>
> Rainer,
>
> First off, good catch on the file descriptors leak.  One additional 
> thing
> you should do is use the socket_close method defined in Utility.h.  
> Reason
> is that this function is portable (Windows does not use close on socket
> descriptors. go figure).
>
> Second, just so you know, the new version being released soon has an
> additional multithreaded implementation of the socket code.  In this
> scenario, each session has it's own thread which not only solves the
> connect problem, it also makes it so sessions that take up a lot of
> processing time (if there are database accesses or whatever when an
> application message is processed) do not interfere with other sessions. 
> The
> single threaded code should still be updated for the reason you pointed
> out, but you will also have another alternative.  Thanks!

Oren,

That's good news! My application callbacks will probably just queue the 
messages and forward them to the main thread, but multiple threads are 
of course the cleanest solution for multiple FIX sessions.

Can you give me a rough estimate when the new version will be out?

Another thing I noticed: The problem reported by Bernard (4.2 tags being 
sent to a 4.0 partner) is pervasive throughout the Session class. I 
wonder if it would not be cleaner to implement 4.0/4.1/4.2 behaviour in 
separate Session subclasses, or "strategy" helper objects?

Thanks for making this an open source project! Unlike many other open 
source efforts, quickfix is exactly what the world needed... :-)

Rainer

Re: [Quickfix-developers] Cannot build quickfix 1.0.4 on Solaris 8

[<OM...@th...>]

looks like you don't have libtool installed.  You can get it here:
http://www.sunfreeware.com/programlistsparc8.html#libtool

libtool is what we use to abstract building libraries on multiple
platforms, you can learn more about it here:
http://www.gnu.org/software/libtool/manual.html

It seems many solaris installations come with an older version or not at
all, which is a shame.  In any case installing it should get rid of this
error.  Let us know if this is the case.

--oren



|---------+----------------------------------------------->
|         |           "Dwight J. Browne"                  |
|         |           <ra...@pa...>                  |
|         |           Sent by:                            |
|         |           qui...@li...ur|
|         |           ceforge.net                         |
|         |                                               |
|         |                                               |
|         |           06/09/2002 09:05 AM                 |
|         |                                               |
|---------+----------------------------------------------->
  >----------------------------------------------------------------------------------------------|
  |                                                                                              |
  |       To:       qui...@li...                                    |
  |       cc:                                                                                    |
  |       Subject:  [Quickfix-developers] Cannot build quickfix 1.0.4 on Solaris 8               |
  >----------------------------------------------------------------------------------------------|




$ gmake
cd . && aclocal
aclocal: configure.in: 25: macro `AM_PROG_LIBTOOL' not found in library
gmake: *** [aclocal.m4] Error 1
$ make
cd . && aclocal
aclocal: configure.in: 25: macro `AM_PROG_LIBTOOL' not found in library
*** Error code 1
make: Fatal error: Command failed for target `aclocal.m4'
uname -a
SunOS growstrong 5.8 Generic_108528-12 sun4u sparc SUNW,Ultra-2

 gcc -v
Reading specs from
/opt/sfw/lib/gcc-lib/sparc-sun-solaris2.8/2.95.2/specs
gcc version 2.95.2 19991024 (release)

Any suggestions?



creating cache ./config.cache
checking for a BSD compatible install... /opt/sfw/bin/ginstall -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... yes
checking for working aclocal... found
checking for working autoconf... found
checking for working automake... found
checking for working autoheader... found
checking for working makeinfo... found
checking for c++... c++
checking whether the C++ compiler (c++ -Wall -fexceptions
-D_XOPEN_SOURCE=500 ) works... yes
checking whether the C++ compiler (c++ -Wall -fexceptions
-D_XOPEN_SOURCE=500 ) is a cross-compiler... no
checking whether we are using GNU C++... yes
checking whether c++ accepts -g... yes
checking for gcc... gcc
checking whether the C compiler (gcc -D_XOPEN_SOURCE=500 ) works... yes
checking whether the C compiler (gcc -D_XOPEN_SOURCE=500 ) is a
cross-compiler... no
checking whether we are using GNU C... yes
checking whether gcc accepts -g... yes
checking host system type... sparc-sun-solaris2.8
checking build system type... sparc-sun-solaris2.8
checking for ranlib... ranlib
checking for ld used by GCC... /usr/ccs/bin/ld
checking if the linker (/usr/ccs/bin/ld) is GNU ld... no
checking for BSD-compatible nm... /usr/local/bin/nm -B
checking whether ln -s works... yes
updating cache ./config.cache
checking for object suffix... o
checking for executable suffix... no
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.lo... yes
checking if gcc supports -fno-rtti -fno-exceptions ... yes
checking if gcc static flag -static works... -static
checking if the linker (/usr/ccs/bin/ld) is GNU ld... no
checking whether the linker (/usr/ccs/bin/ld) supports shared libraries...
yes
checking command to parse /usr/local/bin/nm -B output... ok
checking how to hardcode library paths into programs... immediate
checking for /usr/ccs/bin/ld option to reload object files... -r
checking dynamic linker characteristics... solaris2.8 ld.so
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... no
checking whether to build static libraries... yes
checking for objdir... .libs
creating libtool
loading cache ./config.cache
checking how to run the C preprocessor... gcc -E
checking for flex... flex
checking for flex... (cached) flex
checking for yywrap in -lfl... yes
checking lex output file root... lex.yy
checking whether yytext is a pointer... yes
checking for shutdown in -lc... no
checking for shutdown in -lsocket... yes
checking for inet_addr in -lc... no
checking for inet_addr in -lnsl... yes
checking for stdio.h... yes
checking for STREAMS ioctl... yes
checking for recursive mutexes... yes
checking for typeinfo in the global namespace... no
checking for typeinfo in the std namespace... yes
checking for cplus_demangle in -liberty... yes
checking if select modifies timeval parameter... no
updating cache ./config.cache
creating ./config.status
creating Makefile
creating src/Makefile
creating src/C++/Makefile
creating src/C++/test/Makefile
creating src/java/Makefile
creating src/java/cfg/Makefile
creating src/java/test/Makefile
creating src/java/src/Makefile
creating src/java/src/org/Makefile
creating src/java/src/org/quickfix/Makefile
creating src/java/src/org/quickfix/field/Makefile
creating src/java/src/org/quickfix/fix40/Makefile
creating src/java/src/org/quickfix/fix41/Makefile
creating src/java/src/org/quickfix/fix42/Makefile
creating cfg/Makefile
creating bin/Makefile
creating bin/cfg/Makefile
creating spec/Makefile
creating test/Makefile
creating test/atrun/Makefile
creating test/cfg/Makefile
creating test/definitions/Makefile
creating test/definitions/server/Makefile
creating test/definitions/server/future/Makefile
creating doc/Makefile
creating doc/html/Makefile
creating examples/Makefile
creating examples/ordermatch/Makefile
creating examples/ordermatch/test/Makefile
creating examples/tradeclient/Makefile
creating examples/tradeclientgui/Makefile
creating examples/tradeclientgui/banzai/Makefile
creating examples/tradeclientgui/banzai/cfg/Makefile
creating examples/tradeclientgui/banzai/test/Makefile
creating examples/tradeclientgui/banzai/src/Makefile
creating examples/tradeclientgui/banzai/src/org/Makefile
creating examples/tradeclientgui/banzai/src/org/quickfix/Makefile
creating examples/tradeclientgui/banzai/src/org/quickfix/banzai/Makefile
creating examples/tradeclientgui/banzai/src/org/quickfix/banzai/ui/Makefile
creating templates/Makefile
creating CPPTest/Makefile
creating config.h



 gmake
cd . && aclocal
aclocal: configure.in: 25: macro `AM_PROG_LIBTOOL' not found in library
gmake: *** [aclocal.m4] Error 1


Config.log

This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

configure:566: checking for a BSD compatible install
configure:619: checking whether build environment is sane
configure:676: checking whether make sets ${MAKE}
configure:722: checking for working aclocal
configure:735: checking for working autoconf
configure:748: checking for working automake
configure:761: checking for working autoheader
configure:774: checking for working makeinfo
configure:809: checking for c++
configure:841: checking whether the C++ compiler (c++ -Wall -fexceptions
-D_XOPEN_SOURCE=500 ) works
configure:857: c++ -o conftest -Wall -fexceptions -D_XOPEN_SOURCE=500
conftest.C  1>&5
configure:883: checking whether the C++ compiler (c++ -Wall -fexceptions
-D_XOPEN_SOURCE=500 ) is a cross-compiler
configure:888: checking whether we are using GNU C++
configure:897: c++ -E conftest.C
configure:916: checking whether c++ accepts -g
configure:950: checking for gcc
configure:1063: checking whether the C compiler (gcc -D_XOPEN_SOURCE=500 )
works
configure:1079: gcc -o conftest -D_XOPEN_SOURCE=500   conftest.c  1>&5
configure:1105: checking whether the C compiler (gcc -D_XOPEN_SOURCE=500 )
is a cross-compiler
configure:1110: checking whether we are using GNU C
configure:1119: gcc -E conftest.c
configure:1138: checking whether gcc accepts -g
configure:1247: checking host system type
configure:1268: checking build system type
configure:1288: checking for ranlib
configure:1327: checking for ld used by GCC
configure:1389: checking if the linker (/usr/ccs/bin/ld) is GNU ld
configure:1405: checking for BSD-compatible nm
configure:1441: checking whether ln -s works
ltconfig:603: checking for object suffix
ltconfig:604: gcc -c -D_XOPEN_SOURCE=500  conftest.c 1>&5
ltconfig:629: checking for executable suffix
ltconfig:630: gcc -o conftest -D_XOPEN_SOURCE=500   conftest.c  1>&5
ltconfig:776: checking if gcc PIC flag -fPIC works
ltconfig:777: gcc -c -D_XOPEN_SOURCE=500 -fPIC -DPIC  conftest.c 1>&5
ltconfig:829: checking if gcc supports -c -o file.o
ltconfig:830: gcc -c -D_XOPEN_SOURCE=500 -o out/conftest2.o  conftest.c 1>
&5
ltconfig:862: checking if gcc supports -c -o file.lo
ltconfig:863: gcc -c -D_XOPEN_SOURCE=500 -c -o conftest.lo  conftest.c 1>&5
ltconfig:914: checking if gcc supports -fno-rtti -fno-exceptions
ltconfig:915: gcc -c -D_XOPEN_SOURCE=500 -fno-rtti -fno-exceptions -c
conftest.c  conftest.c 1>&5
ltconfig:958: checking if gcc static flag -static works
ltconfig:959: gcc -o conftest -D_XOPEN_SOURCE=500   -static conftest.c  1>
&5
ltconfig:1653: checking if global_symbol_pipe works
ltconfig:1654: gcc -c -D_XOPEN_SOURCE=500  conftest.c 1>&5
ltconfig:1657: eval "/usr/local/bin/nm -B conftest.o | sed -n -e 's/^.*[
       ]\([ABCDGISTW]\)[             ][          ]*\(\)\([_A-Za-z]
[_A-Za-z0-9]*\)$/\1 \2\3 \3/p' > conftest.nm"
ltconfig:1709: gcc -o conftest -D_XOPEN_SOURCE=500 -fno-builtin -fno-rtti
-fno-exceptions   conftest.c conftstm.o 1>&5
configure:1840: checking how to run the C preprocessor
configure:1861: gcc -E  conftest.c >/dev/null 2>conftest.out
configure:1925: checking for flex
configure:1958: checking for flex
configure:1992: checking for yywrap in -lfl
configure:2011: gcc -o conftest -D_XOPEN_SOURCE=500   conftest.c -lfl   1>
&5
configure:2034: checking lex output file root
configure:2055: checking whether yytext is a pointer
configure:2074: gcc -o conftest -D_XOPEN_SOURCE=500   conftest.c  -lfl 1>&5
configure:2098: checking for shutdown in -lc
configure:2117: gcc -o conftest -D_XOPEN_SOURCE=500   conftest.c -lc   1>&5
Undefined                                  first referenced
 symbol                                        in file
shutdown                            /var/tmp/ccQCxuaR.o
ld: fatal: Symbol referencing errors. No output written to conftest
collect2: ld returned 1 exit status
configure: failed program was:
#line 2106 "configure"
#include "confdefs.h"
/* Override any gcc2 internal prototype to avoid an error.  */
/* We use char because int might match the return type of a gcc2
    builtin and then its argument prototype would still apply.  */
char shutdown();

int main() {
shutdown()
; return 0; }
configure:2136: checking for shutdown in -lsocket
configure:2155: gcc -o conftest -D_XOPEN_SOURCE=500   conftest.c -lsocket
1>&5
configure:2185: checking for inet_addr in -lc
configure:2204: gcc -o conftest -D_XOPEN_SOURCE=500   conftest.c -lc
-lsocket  1>&5
Undefined                                  first referenced
 symbol                                        in file
inet_addr                           /var/tmp/ccyhwbKv.o  (symbol belongs to
implicit dependency /usr/lib/libnsl.so.1)
ld: fatal: Symbol referencing errors. No output written to conftest
collect2: ld returned 1 exit status
configure: failed program was:
#line 2193 "configure"
#include "confdefs.h"
/* Override any gcc2 internal prototype to avoid an error.  */
/* We use char because int might match the return type of a gcc2
    builtin and then its argument prototype would still apply.  */
char inet_addr();

int main() {
inet_addr()
; return 0; }
configure:2223: checking for inet_addr in -lnsl
configure:2242: gcc -o conftest -D_XOPEN_SOURCE=500   conftest.c -lnsl
-lsocket  1>&5
configure:2276: checking for stdio.h
configure:2286: gcc -E  conftest.c >/dev/null 2>conftest.out
configure:2326: checking for STREAMS ioctl
configure:2337: c++ -c -Wall -fexceptions -D_XOPEN_SOURCE=500  conftest.C
1>&5
configure:2351: checking for recursive mutexes
configure:2360: c++ -c -Wall -fexceptions -D_XOPEN_SOURCE=500  conftest.C
1>&5
configure: In function `int main()':
configure:2356: warning: statement with no effect
configure:2373: checking for typeinfo in the global namespace
configure:2382: c++ -c -Wall -fexceptions -D_XOPEN_SOURCE=500  conftest.C
1>&5
configure: In function `int main()':
configure:2378: ANSI C++ forbids declaration `typeinfo' with no type
configure:2378: uninitialized const `typeinfo'
configure:2378: parse error before `&'
configure:2378: warning: unused variable `const int typeinfo'
configure: failed program was:
#line 2375 "configure"
#include "confdefs.h"
#include <typeinfo>
int main() {
const typeinfo& ty = typeid(typeinfo);
; return 0; }
configure:2397: checking for typeinfo in the std namespace
configure:2406: c++ -c -Wall -fexceptions -D_XOPEN_SOURCE=500  conftest.C
1>&5
configure: In function `int main()':
configure:2402: warning: unused variable `const class type_info & ty'
configure:2432: checking for cplus_demangle in -liberty
configure:2451: gcc -o conftest -D_XOPEN_SOURCE=500   conftest.c -liberty
-lnsl -lsocket  1>&5
configure:2478: checking if select modifies timeval parameter
configure:2499: gcc -o conftest -D_XOPEN_SOURCE=500   conftest.c -lnsl
-lsocket  -liberty 1>&5
configure: failed program was:
#line 2483 "configure"
#include "confdefs.h"

#include <unistd.h>
#include <sys/types.h>
#include <sys/time.h>
int main(int argc, char** argv)
{
  struct timeval tv;
  tv.tv_sec = 0;
  tv.tv_usec = 1;
  select(0,0,0,0,&tv);
  return tv.tv_usec != 1 ? 0 : 1;
}

[Quickfix-developers] Cannot build quickfix 1.0.4 on Solaris 8

[Dwight J. B. <ra...@pa...>]

$ gmake
cd . && aclocal
aclocal: configure.in: 25: macro `AM_PROG_LIBTOOL' not found in library
gmake: *** [aclocal.m4] Error 1
$ make
cd . && aclocal
aclocal: configure.in: 25: macro `AM_PROG_LIBTOOL' not found in library
*** Error code 1
make: Fatal error: Command failed for target `aclocal.m4'
uname -a
SunOS growstrong 5.8 Generic_108528-12 sun4u sparc SUNW,Ultra-2

 gcc -v
Reading specs from
/opt/sfw/lib/gcc-lib/sparc-sun-solaris2.8/2.95.2/specs
gcc version 2.95.2 19991024 (release)

Any suggestions?

Re: [Quickfix-developers] Too many open files

[<OM...@th...>]

Rainer,

First off, good catch on the file descriptors leak.  One additional thing
you should do is use the socket_close method defined in Utility.h.  Reason
is that this function is portable (Windows does not use close on socket
descriptors. go figure).

Second, just so you know, the new version being released soon has an
additional multithreaded implementation of the socket code.  In this
scenario, each session has it's own thread which not only solves the
connect problem, it also makes it so sessions that take up a lot of
processing time (if there are database accesses or whatever when an
application message is processed) do not interfere with other sessions. The
single threaded code should still be updated for the reason you pointed
out, but you will also have another alternative.  Thanks!

--oren



|---------+----------------------------------------------->
|         |           Rainer Staringer                    |
|         |           <ra...@aa...>               |
|         |           Sent by:                            |
|         |           qui...@li...ur|
|         |           ceforge.net                         |
|         |                                               |
|         |                                               |
|         |           06/07/2002 08:44 AM                 |
|         |                                               |
|---------+----------------------------------------------->
  >----------------------------------------------------------------------------------------------|
  |                                                                                              |
  |       To:       qui...@li...                                    |
  |       cc:                                                                                    |
  |       Subject:  Re: [Quickfix-developers] Too many open files                                |
  >----------------------------------------------------------------------------------------------|




Ok, found the problem.

SocketConnector::connect seems to be missing a close() in the error case.

   int SocketConnector::connect( const std::string& address, int port )
   {
     int sock = socket(PF_INET, SOCK_STREAM, IPPROTO_TCP);

     sockaddr_in addr;
     addr.sin_family = PF_INET;
     addr.sin_port = htons(port);
     addr.sin_addr.s_addr = inet_addr(socket_hostname(address.c_str()));

     int result = ::connect(sock, reinterpret_cast<sockaddr*>(&addr),
                            sizeof(addr));
     if(result == 0)
       {
         m_monitor.add(sock);
         return sock;
       }
     else
       {
         // Added by rainer.
         close(sock);
         return 0;
       }
   }

There is another problem with this code, in that if one has more than
one FIX session specified in the config file and one of the servers is
unreachable, the whole process (all FIX sessions) will hang on each
reconnect attempt - not good!

Only solution is to put the socket in non-blocking mode and handle the
connect asynchronously. Since I need multiple FIX connections, I might
have a go at it...

Rainer

> On Friday, June 7, 2002, at 02:59 PM, Rainer Staringer wrote:
>
> Hi,
>
> I am developing a FIX client based on quickfix.
>
> I noticed that quickfix (Linux kernel version 2.4.16), when left
> running long enough, uses up all available file descriptors for the
> process, even when only heartbeat messages are exchanged.
>
> Anybody else encountered this problem? Known patch/workaround?
>
> Thanks,
>
> Rainer
>
>
> _______________________________________________________________
>
> Don't miss the 2002 Sprint PCS Application Developer's Conference
> August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
>
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
>


_______________________________________________________________

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm

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

Re: [Quickfix-developers] Too many open files

[Rainer S. <ra...@aa...>]

Ok, found the problem.

SocketConnector::connect seems to be missing a close() in the error case.

   int SocketConnector::connect( const std::string& address, int port )
   {
     int sock = socket(PF_INET, SOCK_STREAM, IPPROTO_TCP);

     sockaddr_in addr;
     addr.sin_family = PF_INET;
     addr.sin_port = htons(port);
     addr.sin_addr.s_addr = inet_addr(socket_hostname(address.c_str()));

     int result = ::connect(sock, reinterpret_cast<sockaddr*>(&addr),
                            sizeof(addr));
     if(result == 0)
       {
         m_monitor.add(sock);
         return sock;
       }
     else
       {
         // Added by rainer.
         close(sock);
         return 0;
       }
   }

There is another problem with this code, in that if one has more than 
one FIX session specified in the config file and one of the servers is 
unreachable, the whole process (all FIX sessions) will hang on each 
reconnect attempt - not good!

Only solution is to put the socket in non-blocking mode and handle the 
connect asynchronously. Since I need multiple FIX connections, I might 
have a go at it...

Rainer

> On Friday, June 7, 2002, at 02:59 PM, Rainer Staringer wrote:
>
> Hi,
>
> I am developing a FIX client based on quickfix.
>
> I noticed that quickfix (Linux kernel version 2.4.16), when left 
> running long enough, uses up all available file descriptors for the 
> process, even when only heartbeat messages are exchanged.
>
> Anybody else encountered this problem? Known patch/workaround?
>
> Thanks,
>
> Rainer
>
>
> _______________________________________________________________
>
> Don't miss the 2002 Sprint PCS Application Developer's Conference
> August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
>
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
>

[Quickfix-developers] Too many open files

[Rainer S. <ra...@aa...>]

Hi,

I am developing a FIX client based on quickfix.

I noticed that quickfix (Linux kernel version 2.4.16), when left running 
long enough, uses up all available file descriptors for the process, 
even when only heartbeat messages are exchanged.

Anybody else encountered this problem? Known patch/workaround?

Thanks,

Rainer

RE: [Quickfix-developers] Segmentation Fault

[<OM...@th...>]

Justin,

When Session::sendToTarget is called, a SessionNotFound exception is thrown
if you try to send to a session that does not exist.  I suspect you are
sending to a session that is not configured in the QuickFIX config file.
You can verify this by changing some of the code so it does some better
error handling.  In the queryEnterOrder function in Application.cpp for
tradeclient, change this code:

if(queryConfirm("Send order"))
    FIX::Session::sendToTarget(order);

to this

if(queryConfirm("Send order"))
{
    try
    {
      FIX::Session::sendToTarget(order);
    }
    catch( FIX::SessionNotFound& e)
    {
        std::cout << "Session does not exist, cannot send message" <<
std::endl;
    }
}

If this message pops up, you know that the session does not exist.

--oren



                                                                                                                                       
                      Justin Pauley                                                                                                    
                      <jp...@fs...>        To:       OM...@th...                                                      
                                               cc:                                                                                     
                      06/06/2002 01:42         Subject:  RE: [Quickfix-developers] Segmentation Fault                                  
                      PM                                                                                                               
                                                                                                                                       
                                                                                                                                       




I am running Linux Kernel:2.4.7-10
gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-98)
It is compiled as:

g++ -g -I../quickfix/include -finline-functions -fexceptions
-D_XOPEN_SOURCE=500 -I. -c tradeclient.cpp

g++ -g -I../quickfix/include -finline-functions -fexceptions
-D_XOPEN_SOURCE=500 -I. -c Application.cpp

g++ -o tradeclient Application.o tradeclient.o -g -L../quickfix/lib
-lquickfix -lpthread -lxml2

I don't have a core file (none was produced) but I do have this from
GDB:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1026 (LWP 2810)]
0x0808233f in _Rb_tree<int, pair<int const, FIX::SocketConnection *>,
_Select1st<pair<int const, FIX::SocketConnection *> >, less<int>,
allocator<FIX::SocketConnection *> >::_M_erase ()
Current language:  auto; currently c

And here is the back trace:
#0  0x0808233f in _Rb_tree<int, pair<int const, FIX::SocketConnection
*>, _Select1st<pair<int const, FIX::SocketConnection *> >, less<int>,
allocator<FIX::SocketConnection *> >::_M_erase ()
#1  0x08082349 in _Rb_tree<int, pair<int const, FIX::SocketConnection
*>, _Select1st<pair<int const, FIX::SocketConnection *> >, less<int>,
allocator<FIX::SocketConnection *> >::_M_erase ()
#2  0x080822c0 in _Rb_tree<int, pair<int const, FIX::SocketConnection
*>, _Select1st<pair<int const, FIX::SocketConnection *> >, less<int>,
allocator<FIX::SocketConnection *> >::clear ()
#3  0x080826a5 in _Rb_tree<int, pair<int const, FIX::SocketConnection
*>, _Select1st<pair<int const, FIX::SocketConnection *> >, less<int>,
allocator<FIX::SocketConnection *> >::~_Rb_tree ()
#4  0x080824ef in map<int, FIX::SocketConnection *, less<int>,
allocator<FIX::SocketConnection *> >::~map ()
#5  0x0805a859 in FIX::SocketInitiator::~SocketInitiator () at
tradeclient.cpp:94
#6  0x08052739 in main (argc=135036920, argv=0x8052728) at
tradeclient.cpp:94
#7  0x400f9811 in find_exception_handler (pc=0x8063f4f, table=0x80c1c38,
eh_info=0x80c7ff8, rethrow=1, cleanup=0x40a83468)
    at ../../gcc/libgcc2.c:3168
#8  0x400f9a62 in throw_helper (eh=0x80c8020, pc=0x8063fa1,
my_udata=0x40a8366c, offset_p=0x40a83668) at ../../gcc/libgcc2.c:3168
#9  0x400f9f4f in __rethrow (index=0x80b71bc) at
../../gcc/libgcc2.c:3168
#10 0x08063fa2 in FIX::FieldMap::getField (this=0x40a83a18,
field=@0x40a8378c)
    at /usr/local/include/quickfix/include/FieldMap.h:115
#11 0x0804e674 in Application::toApp (this=0xbffff9f0,
message=@0x40a83a0c, sessionID=@0x80c4fb0) at Application.cpp:82
#12 0x080540bc in FIX::Session::sendRaw () at tradeclient.cpp:94
#13 0x08053d6c in FIX::Session::send () at tradeclient.cpp:94
#14 0x08058956 in FIX::Session::sendToTarget () at tradeclient.cpp:94
#15 0x0804eaf2 in Application::queryEnterOrder (this=0xbffff9f0,
version=41) at Application.cpp:139
#16 0x0804e8ce in Application::onRun (this=0xbffff9f0) at
Application.cpp:113
#17 0x0805a638 in FIX::Initiator::startThread () at tradeclient.cpp:94
#18 0x40029b9c in pthread_start_thread (arg=0x40a83be0) at manager.c:274
#19 0x40029c7f in pthread_start_thread_event (arg=0x40a83be0) at
manager.c:298


Thanks,
Justin

-----Original Message-----
From: qui...@li...
[mailto:qui...@li...] On Behalf Of
OM...@th...
Sent: Thursday, June 06, 2002 12:25 PM
To: jp...@fs...
Cc: qui...@li...;
qui...@li...
Subject: Re: [Quickfix-developers] Segmentation Fault



Justin,

Can you give some more details.  Are you running on Solaris or Linux,
which kernal?  What version of gcc are you using? Can you also recompile
with the -g option and post the core file so everyone can take a look at
the stack?

--oren



|---------+----------------------------------------------->
|         |           Justin Pauley <jp...@fs...>     |
|         |           Sent by:                            |
|         |           qui...@li...ur|
|         |           ceforge.net                         |
|         |                                               |
|         |                                               |
|         |           06/06/2002 01:04 PM                 |
|         |                                               |
|---------+----------------------------------------------->

>-----------------------------------------------------------------------
-----------------------|
  |
|
  |       To:       qui...@li...
|
  |       cc:
|
  |       Subject:  [Quickfix-developers] Segmentation Fault
|

>-----------------------------------------------------------------------
-----------------------|




I just compiled tradeclient and ordermatch and when I run tradeclient I
get a segmentation Fault? any ideas? Here is the session


Justin





[root@eats tradeclient]# ./tradeclient -f test_conf.cfg


1) Enter Order
2) Cancel Order
3) Replace Order
Action:
Logon - BeginString: FIX.4.1, SenderCompID: direct57, TargetCompID: IB 1


1) FIX.4.0
2) FIX.4.1
3) FIX.4.2
BeginString: 2


NewOrderSingle


1) Market
2) Limit
3) Stop
4) Stop Limit
OrdType: 1


1) Buy
2) Sell
3) Sell Short
4) Sell Short Exempt
5) Cross
6) Cross Short
7) Cross Short Exempt
Side: 1


Symbol: rhat


ClOrdID: 0000


OrderQty: 10


1) Day
2) IOC
3) OPG
4) GTC
5) GTX
TimeInForce: 1


SenderCompID: direct57


TargetCompID: IB


Use a TargetSubID?: n


Send order?: y
Segmentation fault








_______________________________________________________________

Don't miss the 2002 Sprint PCS Application Developer's Conference August
25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm

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