quickfix-developers — QuickFIX developers forum

[Quickfix-developers] reverse dns problem

[H. S. <st...@un...>]

hello everybody,

i just did some tests with quickfix and reverse dns.
the test scenario was like running 2 instances of "executor" on localhost and a third session to a remote host.

if the third host got a reverse dns entry, the connections to the two local executors were pretty fast.
if the third host does NOT have a reverse dns entry, the connection attempts to the local executor instances was HEAVILY slowed down by minutes.
it still connects to the executors, but like a few minutes after starting the initiator process.



could one of you guys verify those behaviour (hopefully on a non-freebsd architecture) and give me some response on how it went?

thanks alot for your help,

heri


-- 
This e-mail may contain confidential and/or privileged information. 
If you are not the intended recipient (or have received this e-mail in error) 
please notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is strictly 
forbidden.

[Quickfix-developers] RE: fromAdmin/fromApp not getting called on Logout from rejected logon

[Jason F. <jf...@ty...>]

After some investigation it appears that a logic_error of "Logon state is
not valid for message" is being thrown in response to the Logout message
being sent from CME, thus resulting in the fromAdmin callback not being
called. Is this expected behavior or a possible bug?

 

Jason

 

  _____  

From: qui...@li...
[mailto:qui...@li...] On Behalf Of Jason
Fagan
Sent: 06 January 2005 15:47
To: qui...@li...
Subject: [Quickfix-developers] fromAdmin/fromApp not getting called on
Logout from rejected logon

 

Can someone please help me before the men in white coats come to take me
away.

 

I am currently developing an application that connects to CME's iLink and I
am trying to run a test where the initial Login is rejected due to a
deliberate incorrect password. CME responds back with a Logout message with
the reason set, but mysteriously the onLogout callback is called but not the
fromAdmin callback, this means that I can not set the next expect sequence
number to the one sent by CME.

 

Is this expected behaviour, am I missing something?

 

Also what is the best way to perform a manual Logon/Logoff, the
SocketInitiator/Session are doing this automatically at the moment and I
would like to perform these myself.

 

Thank you in advance.

 

Jason Fagan

Re: [Quickfix-developers] compatible questions

[Andrew M. <an...@nm...>]

Well.. depending on your situation you may need to do something like this:

1) FIX 4.2 acceptor receives FIX 4.2 message
2) application code instantiates appropriate FIX 4.4 message object
3) FIX 4.4 message's fields are populated with values from FIX 4.2 message
4) FIX 4.4 initiator is handed the 4.4 msg object to be sent.

is that what you mean?

-Andrew


On Thu, 6 Jan 2005, Xizhen Wang wrote:

> Andrew, thank you!
> 
> If that has to be the solution, I will not be able to
> use QuickFix APIs designed specificlly for differently
> FIX versions then. And I have to use those general
> APIs, and then fill in more fields for differently
> verisons in message. Is this correct? or do I miss
> anything?
> 
> Thanks a lot!
> Alvin
> 
> 
> --- Andrew Munn <an...@nm...> wrote:
> 
> > Alvin,
> > you won't be able to pass along a FIX 4.2 message
> > directly into a system 
> > expecting a FIX 4.4 message but you could write an
> > app that has two 
> > sessions, a 4.2 and a 4.4 and some code in between
> > that does the 
> > conversion.  What conversion is necessary will
> > depend on what you're 
> > trading.  Fields are added and removed between
> > versions.
> > 
> > Andrew
> > 
> > On Thu, 6 Jan 2005, Xizhen Wang wrote:
> > 
> > > QuickFIX Documentation:
> >
> http://www.quickfixengine.org/quickfix/doc/html/index.html
> > > QuickFIX FAQ:
> >
> http://www.quickfixengine.org/wikifix/index.php?QuickFixFAQ
> > > QuickFIX Support:
> > http://www.quickfixengine.org/services.html
> > > 
> > > Hi,
> > > 
> > > Beforing going into too many details, I have some
> > > basic questions about QuickFix.
> > > 
> > > 1. Currently, my company will be using FIX 4.4. If
> > a
> > > broker uses FIX 4.2, can the broakers and my
> > company
> > > understand each other? Or the versions have to be
> > > same? 
> > > 
> > > 2. If we need to use both 4.4 and 4.2 to deal with
> > > different brokers, do we have to use different
> > > QuickFIX APIs? If so, does that mean we need to
> > > implement same logics using differently APIs
> > multiple
> > > times? And in the future, do we have to rewrite
> > the
> > > code if we want to upgrade to newer version of
> > FIX?
> > > 
> > > Could you please clarify? Thanks so much!
> > > Alvin
> > > 
> > > 
> > > 
> > > =====
> > > /)_/)
> > > ( ._.)
> > > c(")(")
> > > 
> > > 
> > > 	
> > > 		
> > > __________________________________ 
> > > Do you Yahoo!? 
> > > Yahoo! Mail - You care about security. So do we. 
> > > http://promotions.yahoo.com/new_mail
> > > 
> > > 
> > >
> >
> -------------------------------------------------------
> > > The SF.Net email is sponsored by: Beat the
> > post-holiday blues
> > > Get a FREE limited edition SourceForge.net t-shirt
> > from ThinkGeek.
> > > It's fun and FREE -- well,
> > almost....http://www.thinkgeek.com/sfshirt
> > > _______________________________________________
> > > Quickfix-developers mailing list
> > > Qui...@li...
> > >
> >
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
> > > 
> > 
> 
> 
> =====
> /)_/)
> ( ._.)
> c(")(")
> 
> 
> 	
> 		
> __________________________________ 
> Do you Yahoo!? 
> Yahoo! Mail - You care about security. So do we. 
> http://promotions.yahoo.com/new_mail
> 

Re: [Quickfix-developers] compatible questions

[Xizhen W. <wan...@ya...>]

Andrew, thank you!

If that has to be the solution, I will not be able to
use QuickFix APIs designed specificlly for differently
FIX versions then. And I have to use those general
APIs, and then fill in more fields for differently
verisons in message. Is this correct? or do I miss
anything?

Thanks a lot!
Alvin


--- Andrew Munn <an...@nm...> wrote:

> Alvin,
> you won't be able to pass along a FIX 4.2 message
> directly into a system 
> expecting a FIX 4.4 message but you could write an
> app that has two 
> sessions, a 4.2 and a 4.4 and some code in between
> that does the 
> conversion.  What conversion is necessary will
> depend on what you're 
> trading.  Fields are added and removed between
> versions.
> 
> Andrew
> 
> On Thu, 6 Jan 2005, Xizhen Wang wrote:
> 
> > QuickFIX Documentation:
>
http://www.quickfixengine.org/quickfix/doc/html/index.html
> > QuickFIX FAQ:
>
http://www.quickfixengine.org/wikifix/index.php?QuickFixFAQ
> > QuickFIX Support:
> http://www.quickfixengine.org/services.html
> > 
> > Hi,
> > 
> > Beforing going into too many details, I have some
> > basic questions about QuickFix.
> > 
> > 1. Currently, my company will be using FIX 4.4. If
> a
> > broker uses FIX 4.2, can the broakers and my
> company
> > understand each other? Or the versions have to be
> > same? 
> > 
> > 2. If we need to use both 4.4 and 4.2 to deal with
> > different brokers, do we have to use different
> > QuickFIX APIs? If so, does that mean we need to
> > implement same logics using differently APIs
> multiple
> > times? And in the future, do we have to rewrite
> the
> > code if we want to upgrade to newer version of
> FIX?
> > 
> > Could you please clarify? Thanks so much!
> > Alvin
> > 
> > 
> > 
> > =====
> > /)_/)
> > ( ._.)
> > c(")(")
> > 
> > 
> > 	
> > 		
> > __________________________________ 
> > Do you Yahoo!? 
> > Yahoo! Mail - You care about security. So do we. 
> > http://promotions.yahoo.com/new_mail
> > 
> > 
> >
>
-------------------------------------------------------
> > The SF.Net email is sponsored by: Beat the
> post-holiday blues
> > Get a FREE limited edition SourceForge.net t-shirt
> from ThinkGeek.
> > It's fun and FREE -- well,
> almost....http://www.thinkgeek.com/sfshirt
> > _______________________________________________
> > Quickfix-developers mailing list
> > Qui...@li...
> >
>
https://lists.sourceforge.net/lists/listinfo/quickfix-developers
> > 
> 


=====
/)_/)
( ._.)
c(")(")


	
		
__________________________________ 
Do you Yahoo!? 
Yahoo! Mail - You care about security. So do we. 
http://promotions.yahoo.com/new_mail

Re: [Quickfix-developers] compatible questions

[Andrew M. <an...@nm...>]

Alvin,
you won't be able to pass along a FIX 4.2 message directly into a system 
expecting a FIX 4.4 message but you could write an app that has two 
sessions, a 4.2 and a 4.4 and some code in between that does the 
conversion.  What conversion is necessary will depend on what you're 
trading.  Fields are added and removed between versions.

Andrew

On Thu, 6 Jan 2005, Xizhen Wang wrote:

> QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html
> QuickFIX FAQ: http://www.quickfixengine.org/wikifix/index.php?QuickFixFAQ
> QuickFIX Support: http://www.quickfixengine.org/services.html
> 
> Hi,
> 
> Beforing going into too many details, I have some
> basic questions about QuickFix.
> 
> 1. Currently, my company will be using FIX 4.4. If a
> broker uses FIX 4.2, can the broakers and my company
> understand each other? Or the versions have to be
> same? 
> 
> 2. If we need to use both 4.4 and 4.2 to deal with
> different brokers, do we have to use different
> QuickFIX APIs? If so, does that mean we need to
> implement same logics using differently APIs multiple
> times? And in the future, do we have to rewrite the
> code if we want to upgrade to newer version of FIX?
> 
> Could you please clarify? Thanks so much!
> Alvin
> 
> 
> 
> =====
> /)_/)
> ( ._.)
> c(")(")
> 
> 
> 	
> 		
> __________________________________ 
> Do you Yahoo!? 
> Yahoo! Mail - You care about security. So do we. 
> http://promotions.yahoo.com/new_mail
> 
> 
> -------------------------------------------------------
> The SF.Net email is sponsored by: Beat the post-holiday blues
> Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
> It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
> 

[Quickfix-developers] compatible questions

[Xizhen W. <wan...@ya...>]

Hi,

Beforing going into too many details, I have some
basic questions about QuickFix.

1. Currently, my company will be using FIX 4.4. If a
broker uses FIX 4.2, can the broakers and my company
understand each other? Or the versions have to be
same? 

2. If we need to use both 4.4 and 4.2 to deal with
different brokers, do we have to use different
QuickFIX APIs? If so, does that mean we need to
implement same logics using differently APIs multiple
times? And in the future, do we have to rewrite the
code if we want to upgrade to newer version of FIX?

Could you please clarify? Thanks so much!
Alvin



=====
/)_/)
( ._.)
c(")(")


	
		
__________________________________ 
Do you Yahoo!? 
Yahoo! Mail - You care about security. So do we. 
http://promotions.yahoo.com/new_mail

RE: [Quickfix-developers] Sending time question

[Victor G. <vic...@ch...>]

Barry,

 

Thanks for the reply. I am leaving the CheckLatency and MaxLatency with
their default values: I am receiving market data, so if something gets to me
after 120 seconds, it is pretty worthless. 

 

My concern is with the HeartBeats I send out which do not make it to the
other side in time. I have limited control over the other side, and I want
to make sure I am not delaying the outgoing heartbeats in any way. If,
indeed, field 52 is the timestamp when the message actually goes out on the
socket (and is not sent out at a later time by some thread), I know that I
am doing all I can on my side.

 

Thanks.

 

  _____  

From: Bishop, Barry [mailto:Bar...@gs...] 
Sent: Thursday, January 06, 2005 12:09 PM
To: 'Victor Glava'
Cc: qui...@li...
Subject: RE: [Quickfix-developers] Sending time question

 

Are you aware of the CheckLatency field in the settings file?

 

This could help things at your end.

 

Regards,

barry

-----Original Message-----
From: Victor Glava [mailto:vic...@ch...] 
Sent: Thursday, January 06, 2005 4:39 PM
To: qui...@li...
Subject: [Quickfix-developers] Sending time question

I have a question regarding the sending time in the header... 

When sending any message to a counter party, like the following:

<20050105-20:15:00, FIX.4.4:GATEWAY->ADAPTER, outgoing>

 
(8=FIX.4.4^9=74^35=0^34=34^49=ENLON00WK002^52=20050105-20:15:00.831^56=CTC_M
DAdapterEurex^10=162^)

Is the SendingTime (tag 52) the time the message is actually sent out, or is
it the time when it is placed on a queue, meaning there might be a lag
before the message actually goes out...

My concern is that I am noticing a lag between the time the heart-beat
messages goes out and the time it is received at the other end, which, at
times, causes the other side to logout/disconnect. This might be due to
network delay, but I want to be sure it is not something on my end.

I am using 1.9.4.

Thanks.

RE: [Quickfix-developers] Sending time question

[Bishop, B. <Bar...@gs...>]

Are you aware of the CheckLatency field in the settings file?
 
This could help things at your end.
 
Regards,
barry

-----Original Message-----
From: Victor Glava [mailto:vic...@ch...] 
Sent: Thursday, January 06, 2005 4:39 PM
To: qui...@li...
Subject: [Quickfix-developers] Sending time question



I have a question regarding the sending time in the header... 

When sending any message to a counter party, like the following:

<20050105-20:15:00, FIX.4.4:GATEWAY->ADAPTER, outgoing>

 
(8=FIX.4.4^9=74^35=0^34=34^49=ENLON00WK002^52=20050105-20:15:00.831^56=CTC_M
DAdapterEurex^10=162^)



Is the SendingTime (tag 52) the time the message is actually sent out, or is
it the time when it is placed on a queue, meaning there might be a lag
before the message actually goes out...

My concern is that I am noticing a lag between the time the heart-beat
messages goes out and the time it is received at the other end, which, at
times, causes the other side to logout/disconnect. This might be due to
network delay, but I want to be sure it is not something on my end.

I am using 1.9.4.

Thanks.

[Quickfix-developers] Sending time question

[Victor G. <vic...@ch...>]

I have a question regarding the sending time in the header. 

When sending any message to a counter party, like the following:
<20050105-20:15:00, FIX.4.4:GATEWAY->ADAPTER, outgoing>
 
(8=FIX.4.4^9=74^35=0^34=34^49=ENLON00WK002^52=20050105-20:15:00.831^56=CTC_M
DAdapterEurex^10=162^)

Is the SendingTime (tag 52) the time the message is actually sent out, or is
it the time when it is placed on a queue, meaning there might be a lag
before the message actually goes out.

My concern is that I am noticing a lag between the time the heart-beat
messages goes out and the time it is received at the other end, which, at
times, causes the other side to logout/disconnect. This might be due to
network delay, but I want to be sure it is not something on my end.

I am using 1.9.4.

Thanks.

RE: [Quickfix-developers] starting and stopping socketInitiator()

[Radhika S. <Rad...@Pi...>]

Hi Oren.
Thanks for your reply. I have changed it to use logon() and logoff()

rs


Radhika Sambamurti
Pipeline Trading Systems
Rad...@pi...
212-370-8343

-----Original Message-----
From: qui...@li...
[mailto:qui...@li...] On Behalf Of
Oren Miller
Sent: Wednesday, January 05, 2005 5:08 PM
To: Radhika Sambamurti; qui...@li...
Subject: Re: [Quickfix-developers] starting and stopping
socketInitiator()

QuickFIX Documentation:
http://www.quickfixengine.org/quickfix/doc/html/index.html
QuickFIX FAQ:
http://www.quickfixengine.org/wikifix/index.php?QuickFixFAQ
QuickFIX Support: http://www.quickfixengine.org/services.html

Stopping and restarting initiators doesn't really work right now.
Instead you should use the logoff and logon commands on your sessions.

--oren

----- Original Message -----
From: "Radhika Sambamurti" <Rad...@Pi...>
To: <qui...@li...>
Sent: Monday, January 03, 2005 10:17 AM
Subject: [Quickfix-developers] starting and stopping socketInitiator()


QuickFIX Documentation:=20
http://www.quickfixengine.org/quickfix/doc/html/index.html
QuickFIX FAQ:
http://www.quickfixengine.org/wikifix/index.php?QuickFixFAQ
QuickFIX Support: http://www.quickfixengine.org/services.html

Hi,

I have been able to analyze my session problems to the way I start and
stop socketInitiator().

The first time the app starts - socketInitiator is started and when I
logoff a session, socketInitiator is stopped.
When I start socketInitiator and try to logon, onLogon is not called,
and the session never logs on.
I am not exiting my application when I logoff a session and stop the
SocketInitiator.

I see a few emails about this question. Is anyone starting, stopping,
and starting socketInitiator for every session?

Thanks,
Radhika


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Quickfix-developers mailing list
Qui...@li...
https://lists.sourceforge.net/lists/listinfo/quickfix-developers



-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Quickfix-developers mailing list
Qui...@li...
https://lists.sourceforge.net/lists/listinfo/quickfix-developers

[Quickfix-developers] fromAdmin/fromApp not getting called on Logout from rejected logon

[Jason F. <jf...@ty...>]

Can someone please help me before the men in white coats come to take me
away.

 

I am currently developing an application that connects to CME's iLink and I
am trying to run a test where the initial Login is rejected due to a
deliberate incorrect password. CME responds back with a Logout message with
the reason set, but mysteriously the onLogout callback is called but not the
fromAdmin callback, this means that I can not set the next expect sequence
number to the one sent by CME.

 

Is this expected behaviour, am I missing something?

 

Also what is the best way to perform a manual Logon/Logoff, the
SocketInitiator/Session are doing this automatically at the moment and I
would like to perform these myself.

 

Thank you in advance.

 

Jason Fagan

Re: [Quickfix-developers] ScreenLogFactory

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

You need to implement the Log and LogFactory interfaces.  Be careful =
about threading issues.  If you are using start()  to initiate QuickFIX, =
the log reports will not be coming on your main application thread.  =
This may be a problem for your UI components.  So you would either need =
to use QuickFIX single threaded with polling, or use the log to get your =
messages to your application thread so they can be displayed.

--oren
  ----- Original Message -----=20
  From: Gustavo C. Jacob=20
  To: qui...@li...=20
  Sent: Monday, January 03, 2005 12:01 PM
  Subject: [Quickfix-developers] ScreenLogFactory


  Hi there,

  =20

  =20

  I'm new to Fix and I'm trying to send the logs of the engine to a text =
box on a form instead of to the default output.

  =20

  Is this possible?

  How?

  =20

  Tanks in advance.

  =20

  =20

  =20

  Gustavo Chiamolera Jacob
  HZB Consultoria Financeira
  55-11-4501-2033

  =20

Re: [Quickfix-developers] starting and stopping socketInitiator()

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

Stopping and restarting initiators doesn't really work right now.  Instead 
you should use the logoff and logon commands on your sessions.

--oren

----- Original Message ----- 
From: "Radhika Sambamurti" <Rad...@Pi...>
To: <qui...@li...>
Sent: Monday, January 03, 2005 10:17 AM
Subject: [Quickfix-developers] starting and stopping socketInitiator()


QuickFIX Documentation: 
http://www.quickfixengine.org/quickfix/doc/html/index.html
QuickFIX FAQ: http://www.quickfixengine.org/wikifix/index.php?QuickFixFAQ
QuickFIX Support: http://www.quickfixengine.org/services.html

Hi,

I have been able to analyze my session problems to the way I start and
stop socketInitiator().

The first time the app starts - socketInitiator is started and when I
logoff a session, socketInitiator is stopped.
When I start socketInitiator and try to logon, onLogon is not called,
and the session never logs on.
I am not exiting my application when I logoff a session and stop the
SocketInitiator.

I see a few emails about this question. Is anyone starting, stopping,
and starting socketInitiator for every session?

Thanks,
Radhika


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Quickfix-developers mailing list
Qui...@li...
https://lists.sourceforge.net/lists/listinfo/quickfix-developers

Re: [Quickfix-developers] UnsatisfiedLinkError

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

The binaries that we distribute are compiled with the default build 
settings.  This means they are not build with MySQL support.  If you need 
MySQL support, you will need to build from source.

--oren

----- Original Message ----- 
From: "Xizhen Wang" <wan...@ya...>
To: <qui...@li...>
Sent: Monday, January 03, 2005 4:22 PM
Subject: [Quickfix-developers] UnsatisfiedLinkError


> QuickFIX Documentation: 
> http://www.quickfixengine.org/quickfix/doc/html/index.html
> QuickFIX FAQ: http://www.quickfixengine.org/wikifix/index.php?QuickFixFAQ
> QuickFIX Support: http://www.quickfixengine.org/services.html
>
> Hi,
>
> I got an "UnsatisfiedLinkError" when I run quickfix.
> The document says, "You havn't built quickfix or the
> JNI wrapper with MySQL support". I just want to make
> sure that the existing quickfix_jni.dll file that came
> with installation was not build with MySQL support.
>
> If that's the case, is there any place where I can
> download the dll file with MySQL support? Or I have to
> build myself?
>
> Thanks!
>
>
>
> =====
> /)_/)
> ( ._.)
> c(")(")
>
>
>
> __________________________________
> Do you Yahoo!?
> Take Yahoo! Mail with you! Get it on your mobile phone.
> http://mobile.yahoo.com/maildemo
>
>
> -------------------------------------------------------
> The SF.Net email is sponsored by: Beat the post-holiday blues
> Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
> It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
> 

RE: [Quickfix-developers] CME XML Spec File

[<em...@co...>]

Jason,
 
As you know CME requires tag 789 in the logout message. 
 
What I have done is modified the Session class of the QuickFix engine a
little bit by adding a 'generateLogout' method that is a public member, as
well as adding a 'logoff' method to the SocketInitiator and
ThreadedSocketInitiator that is public and takes the SessionID as the
parameter.
 
So then I have the following:
SocketInitiator extension

void SocketInitiator::logoff(const SessionID& sessionID)
{ QF_STACK_PUSH(SocketInitiator::logoff)
    Session* pSession = Session::lookupSession(sessionID);
    if(pSession)
        pSession->generateLogout(-1);
QF_STACK_POP
}

Session extension

void Session::generateLogout( int error )
{ QF_STACK_PUSH(Session::generateLogout)

Message logout;
logout.getHeader().setField( MsgType( MsgType_Logout ) );
int nNextSeqNum_ = getExpectedSenderNum();
IntField next_expected_sequence_number(789, nNextSeqNum_);
logout.setField(next_expected_sequence_number);
fill( logout.getHeader() );
sendRaw( logout );
m_state.sentLogout( true );

QF_STACK_POP
}

 

The reason I have done this is because all the sequence numbers are stored
within the QuickFix engine module. It was done as a quick solution and there
are probably much better ways of handling this.
Actually just looking at it now, a much better way of doing this is by
adding this tag in the 'toAdmin' method.

You already probably have :

Header& header_ = msg.getHeader();
eader_.setField(fix_sender_sub_id_);
header_.setField(fix_sender_location_id_);
header_.setField(fix_target_sub_id_);

so just add the following:

Session* pSession = Session::lookupSession(sessionID);

ATLASSERT(pSession); //throw some kind of exception here if it is NULL, not
gonna write code for that now

int nNextSeqNum_ = pSession->getExpectedSenderNum();
IntField next_expected_sequence_number(789, nNextSeqNum_);
msg.setField(next_expected_sequence_number);

It should be ass simple as that although have not tried it this way.

The reason I have extended the SocketInitator and Session classes is because
I wanted to have the ability to call logoff when I wanted to.

Generally, I would advise you to modify the message to cope with
non-standard fields when you are actually constructing the message, as you
are going to have a number of non-standard fields for CME in order
submission, order pulling, etc.

Hope that helps.

Regards,

Emir Kamber

 

-----Original Message-----
From: Jason Fagan [mailto:jf...@ty...]
Sent: Wednesday, January 05, 2005 4:29 PM
To: em...@co...
Subject: RE: [Quickfix-developers] CME XML Spec File



Emir,

 

Is it possible I am using the wrong approach? When receiving a logout
message QuickFIX rejected it because of the non-standard field 789 in the
message.

 

Where is the best place to modify the message to cope with non-standard
fields, the fromAdmin callback or in the message definitions?

 

Regards

 

Jason

 


   _____  


From: qui...@li...
[mailto:qui...@li...] On Behalf Of
em...@co...
Sent: 05 January 2005 15:42
To: jf...@ty...
Cc: qui...@li...
Subject: RE: [Quickfix-developers] CME XML Spec File

 

Jason,

 

I have successfully developed to CME's iLink 2 but have not used a spec file
for it. Why do you want to use an XML spec file when you already have all
the definitions you need in the appropriate fix42 header files supplied. 

 

The application we developed is a stand-alone that connects to both the
iLink gateway and the market-data feed from the MD boxes.

 

Regards,

 

Emir Kamber

-----Original Message-----
From: Jason Fagan [mailto:jf...@ty...]
Sent: Wednesday, January 05, 2005 3:01 PM
To: qui...@li...
Subject: [Quickfix-developers] CME XML Spec File

Hi,

 

Would anyone happen to have a FIX spec file for CME's iLink 2 that they
would be happy to share? 

 

Regards

 

Jason Fagan

 

---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.766 / Virus Database: 513 - Release Date: 9/17/2004


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.766 / Virus Database: 513 - Release Date: 9/17/2004



---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.766 / Virus Database: 513 - Release Date: 9/17/2004



---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.766 / Virus Database: 513 - Release Date: 9/17/2004
 

RE: [Quickfix-developers] CME XML Spec File

[<em...@co...>]

Jason,
 
I have successfully developed to CME's iLink 2 but have not used a spec file
for it. Why do you want to use an XML spec file when you already have all
the definitions you need in the appropriate fix42 header files supplied. 
 
The application we developed is a stand-alone that connects to both the
iLink gateway and the market-data feed from the MD boxes.
 
Regards,
 
Emir Kamber

-----Original Message-----
From: Jason Fagan [mailto:jf...@ty...]
Sent: Wednesday, January 05, 2005 3:01 PM
To: qui...@li...
Subject: [Quickfix-developers] CME XML Spec File



Hi,

 

Would anyone happen to have a FIX spec file for CME's iLink 2 that they
would be happy to share? 

 

Regards

 

Jason Fagan


---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.766 / Virus Database: 513 - Release Date: 9/17/2004



---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.766 / Virus Database: 513 - Release Date: 9/17/2004
 

[Quickfix-developers] CME XML Spec File

[Jason F. <jf...@ty...>]

Hi,

 

Would anyone happen to have a FIX spec file for CME's iLink 2 that they
would be happy to share? 

 

Regards

 

Jason Fagan

RE: [Quickfix-developers] Logout Timeout

[Jason F. <jf...@ty...>]

Oren

Thanks for a quick reply. I've already upped the number which solved my
problems of missing the logout message, straight away, so I'll sit tight =
for
the next release.

Jason

-----Original Message-----
From: qui...@li...
[mailto:qui...@li...] On Behalf Of =
Oren
Miller
Sent: 05 January 2005 14:52
To: Jason Fagan
Cc: qui...@li...
Subject: Re: [Quickfix-developers] Logout Timeout

QuickFIX Documentation:
http://www.quickfixengine.org/quickfix/doc/html/index.html
QuickFIX FAQ: =
http://www.quickfixengine.org/wikifix/index.php?QuickFixFAQ
QuickFIX Support: http://www.quickfixengine.org/services.html

Yes Jason, it is currently hardcoded to the value recommended by the=20
specification.  We have already received a patch for turning this into=20
a parameter, so if you like you can do less work and just increase the=20
timeout to something larger. The next release will have this parameter.

--oren

On Jan 5, 2005, at 2:43 AM, Jason Fagan wrote:

> Hi,
>
> =A0
>
> I have just started using QuickFIX 1.9.4 in an application connecting=20
> to CME and I have run into a minor problem with timeouts when waiting=20
> for the Logout message from the exchange. After looking at the code I=20
> see that in SessionState.h line 97 there is a hard-wired value of 2.
>
> =A0
>
> Before I modify the code to make this a configurable parameter I=20
> wanted to check if my assumptions are right and if I make the changes=20
> can I submit them for inclusion in the next release?
>
> =A0
>
> Regards,
>
> =A0
>
> Jason Fagan



-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Quickfix-developers mailing list
Qui...@li...
https://lists.sourceforge.net/lists/listinfo/quickfix-developers

Re: [Quickfix-developers] Logout Timeout

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

Yes Jason, it is currently hardcoded to the value recommended by the=20
specification.  We have already received a patch for turning this into=20=

a parameter, so if you like you can do less work and just increase the=20=

timeout to something larger. The next release will have this parameter.

--oren

On Jan 5, 2005, at 2:43 AM, Jason Fagan wrote:

> Hi,
>
> =A0
>
> I have just started using QuickFIX 1.9.4 in an application connecting=20=

> to CME and I have run into a minor problem with timeouts when waiting=20=

> for the Logout message from the exchange. After looking at the code I=20=

> see that in SessionState.h line 97 there is a hard-wired value of 2.
>
> =A0
>
> Before I modify the code to make this a configurable parameter I=20
> wanted to check if my assumptions are right and if I make the changes=20=

> can I submit them for inclusion in the next release?
>
> =A0
>
> Regards,
>
> =A0
>
> Jason Fagan

[Quickfix-developers] Logout Timeout

[Jason F. <jf...@ty...>]

Hi,

 

I have just started using QuickFIX 1.9.4 in an application connecting to CME
and I have run into a minor problem with timeouts when waiting for the
Logout message from the exchange. After looking at the code I see that in
SessionState.h line 97 there is a hard-wired value of 2.

 

Before I modify the code to make this a configurable parameter I wanted to
check if my assumptions are right and if I make the changes can I submit
them for inclusion in the next release?

 

Regards,

 

Jason Fagan

[Quickfix-developers] QF Binaries for Windows x64 on AMD64 available.

[Andrew M. <an...@nm...>]

These appear to work fine.  MySQL support was not compiled in.  MS is 
making a 360 day free trial of Windows x64 available at
http://www.microsoft.com/windowsxp/64bit/evaluation/upgrade.mspx

QF bins at http://www.nmedia.net/~andrew/quickfix_amd64/

If anyone tests these and finds issues please let me know.

Thanks,
Andrew Munn

Re: [Quickfix-developers] Compiling quickfix for AMD Opteron on WinXP

[Andrew M. <an...@nm...>]

Correction: My quickfix.lib (AMD64) appears to compile file.  It is still 
untested.  I have not compiled the dll successfully yet.

Thanks,
Andrew Munn

On Tue, 4 Jan 2005, Andrew Munn wrote:

> QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html
> QuickFIX FAQ: http://www.quickfixengine.org/wikifix/index.php?QuickFixFAQ
> QuickFIX Support: http://www.quickfixengine.org/services.html
> 
> I am getting these errors when compiling quickfix_jni.dll for AMD64 using 
> Visual Studio 2005 Beta1 on XP x64.  My quickfix.dll appears to compile 
> fine. My compiled qickfix.lib is 15,486,330 bytes opposed to the 32bit 
> windows one which is roughly half that size.  The machine is a 2-way Opteron.  
> 
> My 64 bit Win/AMD64 build is at:
> www.nmedia.net/~andrew/quickfix.lib
> 
> Is the problem below because I am trying to link an AMD64 .dll with a 
> win32 binary dist provided libmysql.lib?  Do I need to build an AMD64 
> specific version of MySQL?
> 
> 
> Command line options used are:
> /I "C:\MySQL\include" /I "../../include" /D "_WINDOWS" /D "_USRDLL" /D 
> "QUICKFIX_JNI_EXPORTS" /D "_WINDLL" /D "_MBCS" /GF /FD /EHsc /MD /Gy 
> /Fp".\Release/quickfix_jni.pch" /Fo".\Release/" /Fd".\Release/" /nologo /c 
> /Wp64
> 
> 	Error	337		error LNK2019: unresolved external symbol 
> mysql_close referenced in function "public: virtual __cdecl 
> FIX::MySQLLog::~MySQLLog(void)" (??1MySQLLog@FIX@@UEAA@XZ)	
> quickfix_jni					
> 	Error	338		error LNK2001: unresolved external symbol 
> mysql_close	quickfix_jni					
> 	Error	339		error LNK2019: unresolved external symbol 
> mysql_real_connect referenced in function "public: __cdecl 
> FIX::MySQLLog::MySQLLog(class FIX::SessionID const &,class 
> std::basic_string<char,struct std::char_traits<char>,class 
> std::allocator<char> > const &,class std::basic_string<char,struct 
> std::char_traits<char>,class std::allocator<char> > const &,class 
> std::basic_string<char,struct std::char_traits<char>,class 
> std::allocator<char> > const &,class std::basic_string<char,struct 
> std::char_traits<char>,class std::allocator<char> > const &,short)" 
> (??0MySQLLog@FIX@@QEAA@AEBVSessionID@1@AEBV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@111F@Z)	
> quickfix_jni					
> 	Error	340		error LNK2001: unresolved external symbol 
> mysql_real_connect	quickfix_jni					
> 	Error	341		error LNK2019: unresolved external symbol 
> mysql_init referenced in function "public: __cdecl 
> FIX::MySQLLog::MySQLLog(class FIX::SessionID const &,class 
> std::basic_string<char,struct std::char_traits<char>,class 
> std::allocator<char> > const &,class std::basic_string<char,struct 
> std::char_traits<char>,class std::allocator<char> > const &,class 
> std::basic_string<char,struct std::char_traits<char>,class 
> std::allocator<char> > const &,class std::basic_string<char,struct 
> std::char_traits<char>,class std::allocator<char> > const &,short)" 
> (??0MySQLLog@FIX@@QEAA@AEBVSessionID@1@AEBV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@111F@Z)	
> quickfix_jni					
> 	Error	342		error LNK2001: unresolved external symbol 
> mysql_init	quickfix_jni					
> 	Error	343		error LNK2019: unresolved external symbol 
> mysql_query referenced in function "private: void __cdecl 
> FIX::MySQLLog::insert(class std::basic_string<char,struct 
> std::char_traits<char>,class std::allocator<char> > const &,class 
> std::basic_string<char,struct std::char_traits<char>,class 
> std::allocator<char> >)" 
> (?insert@MySQLLog@FIX@@AEAAXAEBV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@V34@@Z)	
> quickfix_jni					
> 	Error	344		error LNK2001: unresolved external symbol 
> mysql_query	quickfix_jni					
> 	Error	345		error LNK2019: unresolved external symbol 
> mysql_errno referenced in function "int __cdecl FIX::safe_query(struct 
> st_mysql *,class std::basic_string<char,struct 
> std::char_traits<char>,class std::allocator<char> > const &)" 
> (?safe_query@FIX@@YAHPEAUst_mysql@@AEBV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@Z)	
> quickfix_jni					
> 	Error	346		error LNK2019: unresolved external symbol 
> mysql_free_result referenced in function "private: void __cdecl 
> FIX::MySQLStore::populateCache(void)" 
> (?populateCache@MySQLStore@FIX@@AEAAXXZ)	quickfix_jni					
> 	Error	347		error LNK2019: unresolved external symbol 
> mysql_fetch_row referenced in function "private: void __cdecl 
> FIX::MySQLStore::populateCache(void)" 
> (?populateCache@MySQLStore@FIX@@AEAAXXZ)	quickfix_jni					
> 	Error	348		error LNK2019: unresolved external symbol 
> mysql_num_rows referenced in function "private: void __cdecl 
> FIX::MySQLStore::populateCache(void)" 
> (?populateCache@MySQLStore@FIX@@AEAAXXZ)	quickfix_jni					
> 	Error	349		error LNK2019: unresolved external symbol 
> mysql_store_result referenced in function "private: void __cdecl 
> FIX::MySQLStore::populateCache(void)" 
> (?populateCache@MySQLStore@FIX@@AEAAXXZ)	quickfix_jni					
> 	Error	350		fatal error LNK1120: 9 unresolved 
> externals	quickfix_jni					
> 
> 
> 
> 
> 
> -------------------------------------------------------
> The SF.Net email is sponsored by: Beat the post-holiday blues
> Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
> It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
> 

[Quickfix-developers] Compiling quickfix for AMD Opteron on WinXP

[Andrew M. <an...@nm...>]

I am getting these errors when compiling quickfix_jni.dll for AMD64 using 
Visual Studio 2005 Beta1 on XP x64.  My quickfix.dll appears to compile 
fine. My compiled qickfix.lib is 15,486,330 bytes opposed to the 32bit 
windows one which is roughly half that size.  The machine is a 2-way Opteron.  

My 64 bit Win/AMD64 build is at:
www.nmedia.net/~andrew/quickfix.lib

Is the problem below because I am trying to link an AMD64 .dll with a 
win32 binary dist provided libmysql.lib?  Do I need to build an AMD64 
specific version of MySQL?


Command line options used are:
/I "C:\MySQL\include" /I "../../include" /D "_WINDOWS" /D "_USRDLL" /D 
"QUICKFIX_JNI_EXPORTS" /D "_WINDLL" /D "_MBCS" /GF /FD /EHsc /MD /Gy 
/Fp".\Release/quickfix_jni.pch" /Fo".\Release/" /Fd".\Release/" /nologo /c 
/Wp64

	Error	337		error LNK2019: unresolved external symbol 
mysql_close referenced in function "public: virtual __cdecl 
FIX::MySQLLog::~MySQLLog(void)" (??1MySQLLog@FIX@@UEAA@XZ)	
quickfix_jni					
	Error	338		error LNK2001: unresolved external symbol 
mysql_close	quickfix_jni					
	Error	339		error LNK2019: unresolved external symbol 
mysql_real_connect referenced in function "public: __cdecl 
FIX::MySQLLog::MySQLLog(class FIX::SessionID const &,class 
std::basic_string<char,struct std::char_traits<char>,class 
std::allocator<char> > const &,class std::basic_string<char,struct 
std::char_traits<char>,class std::allocator<char> > const &,class 
std::basic_string<char,struct std::char_traits<char>,class 
std::allocator<char> > const &,class std::basic_string<char,struct 
std::char_traits<char>,class std::allocator<char> > const &,short)" 
(??0MySQLLog@FIX@@QEAA@AEBVSessionID@1@AEBV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@111F@Z)	
quickfix_jni					
	Error	340		error LNK2001: unresolved external symbol 
mysql_real_connect	quickfix_jni					
	Error	341		error LNK2019: unresolved external symbol 
mysql_init referenced in function "public: __cdecl 
FIX::MySQLLog::MySQLLog(class FIX::SessionID const &,class 
std::basic_string<char,struct std::char_traits<char>,class 
std::allocator<char> > const &,class std::basic_string<char,struct 
std::char_traits<char>,class std::allocator<char> > const &,class 
std::basic_string<char,struct std::char_traits<char>,class 
std::allocator<char> > const &,class std::basic_string<char,struct 
std::char_traits<char>,class std::allocator<char> > const &,short)" 
(??0MySQLLog@FIX@@QEAA@AEBVSessionID@1@AEBV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@111F@Z)	
quickfix_jni					
	Error	342		error LNK2001: unresolved external symbol 
mysql_init	quickfix_jni					
	Error	343		error LNK2019: unresolved external symbol 
mysql_query referenced in function "private: void __cdecl 
FIX::MySQLLog::insert(class std::basic_string<char,struct 
std::char_traits<char>,class std::allocator<char> > const &,class 
std::basic_string<char,struct std::char_traits<char>,class 
std::allocator<char> >)" 
(?insert@MySQLLog@FIX@@AEAAXAEBV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@V34@@Z)	
quickfix_jni					
	Error	344		error LNK2001: unresolved external symbol 
mysql_query	quickfix_jni					
	Error	345		error LNK2019: unresolved external symbol 
mysql_errno referenced in function "int __cdecl FIX::safe_query(struct 
st_mysql *,class std::basic_string<char,struct 
std::char_traits<char>,class std::allocator<char> > const &)" 
(?safe_query@FIX@@YAHPEAUst_mysql@@AEBV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@Z)	
quickfix_jni					
	Error	346		error LNK2019: unresolved external symbol 
mysql_free_result referenced in function "private: void __cdecl 
FIX::MySQLStore::populateCache(void)" 
(?populateCache@MySQLStore@FIX@@AEAAXXZ)	quickfix_jni					
	Error	347		error LNK2019: unresolved external symbol 
mysql_fetch_row referenced in function "private: void __cdecl 
FIX::MySQLStore::populateCache(void)" 
(?populateCache@MySQLStore@FIX@@AEAAXXZ)	quickfix_jni					
	Error	348		error LNK2019: unresolved external symbol 
mysql_num_rows referenced in function "private: void __cdecl 
FIX::MySQLStore::populateCache(void)" 
(?populateCache@MySQLStore@FIX@@AEAAXXZ)	quickfix_jni					
	Error	349		error LNK2019: unresolved external symbol 
mysql_store_result referenced in function "private: void __cdecl 
FIX::MySQLStore::populateCache(void)" 
(?populateCache@MySQLStore@FIX@@AEAAXXZ)	quickfix_jni					
	Error	350		fatal error LNK1120: 9 unresolved 
externals	quickfix_jni					

[Quickfix-developers] [FileLog] Make members protected, not private

[Caleb E. <cal...@gm...>]

Here is a patch that lets users derive from the FileLog class and
initialize/access the output streams in a different way.

Index: quickfix/src/C++/FileLog.h
===================================================================
RCS file: /cvsroot/quickfix/quickfix/src/C++/FileLog.h,v
retrieving revision 1.5
diff -u -b -r1.5 FileLog.h
--- quickfix/src/C++/FileLog.h  28 Dec 2004 15:23:26 -0000      1.5
+++ quickfix/src/C++/FileLog.h  4 Jan 2005 14:27:43 -0000
@@ -86,7 +86,7 @@
     << " : " << value << std::endl << std::flush;
   }
 
-private:
+protected:
   SessionID m_sessionID;
   std::ofstream m_incoming;
   std::ofstream m_outgoing;

-- 
Caleb Epstein
caleb dot epstein at gmail dot com

Re: [Quickfix-developers] Problem on compiling with MySQL

[Caleb E. <cal...@gm...>]

On Solaris I don't believe you can link a shared library against a
static one, and thats what seems to be happening here.  You'll need to
build and link with a shared library version of libmysqlclient.


On Tue, 4 Jan 2005 16:19:23 +0800, Steven Leung
<ste...@2g...> wrote:
> =20
> =20
>=20
> Here are more detail errors, and it seems it related to MySQL since the m=
ake
> install is ok when not compiling with MySQL=20
>=20
>  =20
>=20
> =E2=80=A6=E2=80=A6.=20
>=20
> g++ -shared -nostdlib  /usr/local/lib/gcc/sparc-sun-solaris2.8/3.4.2/crti=
.o
> /usr/ccs/lib/values-Xa.o
> /usr/local/lib/gcc/sparc-sun-solaris2.8/3.4.2/crtbegin.o  .libs/JVM.o
> .libs/Conversions.o .libs/JavaApplication.o .libs/JavaLog.o
> .libs/JavaLogFactory.o .libs/JavaMessageStore.o
> .libs/JavaMessageStoreFactory.o .libs/quickfix_DataDictionary.o
> .libs/quickfix_FileStore.o .libs/quickfix_FileStoreFactory.o
> .libs/quickfix_FileLog.o .libs/quickfix_FileLogFactory.o
> .libs/quickfix_Group.o .libs/quickfix_CppMessageStore.o
> .libs/quickfix_MemoryStore.o .libs/quickfix_Message.o
> .libs/quickfix_MySQLStore.o .libs/quickfix_MySQLStoreFactory.o
> .libs/quickfix_CppLog.o .libs/quickfix_MySQLLog.o
> .libs/quickfix_MySQLLogFactory.o .libs/quickfix_ScreenLog.o
> .libs/quickfix_ScreenLogFactory.o .libs/quickfix_Session.o
> .libs/quickfix_SessionID.o .libs/quickfix_SessionSettings.o
> .libs/quickfix_SocketAcceptor.o .libs/quickfix_SocketInitiator.o
> .libs/quickfix_ThreadedSocketAcceptor.o
> .libs/quickfix_ThreadedSocketInitiator.o  -Wl,-R -Wl,/usr/local/lib -Wl,-=
R
> -Wl,/usr/local/mysql/lib/mysql -L/usr/local/lib/../sparc-sun-solaris2.8/l=
ib
> -L/usr/local/sparc-sun-solaris2.8/lib -L/usr/local/sparc-sun-solaris2.8/b=
in
> -L/usr2/SOURCES/S8/gcc-3.4.2/objdir/gcc
> -L/usr2/SOURCES/S8/gcc-3.4.2/objdir/sparc-sun-solaris2.8/libstdc++-v3/src=
/.libs
> -L/usr2/SOURCES/S8/gcc-3.4.2/objdir/sparc-sun-solaris2.8/libstdc++-v3/src
> -L/usr/local/mysql/lib/mysql -L/usr/local/BerkeleyDB.4.1/lib
> -L/usr/local/ssl/lib -L/usr/openwin/lib -L/usr/lib -L/usr/local/lib
> -lquickfix -lrt -lxml2 -lz -lpthread -liconv -lsocket -lnsl -lmysqlclient
> -liberty -L/usr/local/lib/gcc/sparc-sun-solaris2.8/3.4.2
> -L/usr/local/lib/gcc/sparc-sun-solaris2.8/3.4.2/../../../../sparc-sun-sol=
aris2.8/lib
> -L/usr/ccs/bin -L/usr/ccs/lib
> -L/usr/local/lib/gcc/sparc-sun-solaris2.8/3.4.2/../../.. -lstdc++ -lm
> -lgcc_s /usr/local/lib/gcc/sparc-sun-solaris2.8/3.4.2/crtend.o
> /usr/local/lib/gcc/sparc-sun-solaris2.8/3.4.2/crtn.o  -Wl,-h
> -Wl,libquickfix_jni.so.9 -o .libs/libquickfix_jni.so.9.0.0=20
>=20
> Text relocation remains                         referenced=20
>=20
>     against symbol                  offset      in file=20
>=20
> <unknown>                           0x524     =20
> /usr/local/mysql/lib/mysql/libmysqlclient.a(libmysql.o)=20
>=20
> <unknown>                           0x528     =20
> /usr/local/mysql/lib/mysql/libmysqlclient.a(libmysql.o)=20
>=20
> <unknown>                           0x52c     =20
> /usr/local/mysql/lib/mysql/libmysqlclient.a(libmysql.o)=20
>=20
> <unknown>                           0x530     =20
> /usr/local/mysql/lib/mysql/libmysqlclient.a(libmysql.o)=20
>=20
> <unknown>                           0x534     =20
> /usr/local/mysql/lib/mysql/libmysqlclient.a(libmysql.o)=20
>=20
> <unknown>                           0x538     =20
> /usr/local/mysql/lib/mysql/libmysqlclient.a(libmysql.o)=20
>=20
> <unknown>                           0x53c     =20
> /usr/local/mysql/lib/mysql/libmysqlclient.a(libmysql.o)=20
>=20
> <unknown>                           0x540     =20
> /usr/local/mysql/lib/mysql/libmysqlclient.a(libmysql.o)=20
>=20
> <unknown>                           0x544     =20
> /usr/local/mysql/lib/mysql/libmysqlclient.a(libmysql.o)=20
>=20
> <unknown>                           0x548     =20
> /usr/local/mysql/lib/mysql/libmysqlclient.a(libmysql.o)=20
>=20
> <unknown>                           0x54c     =20
> /usr/local/mysql/lib/mysql/libmysqlclient.a(libmysql.o)=20
>=20
> <unknown>                           0x550     =20
> /usr/local/mysql/lib/mysql/libmysqlclient.a(libmysql.o)=20
>=20
> <unknown>                           0x554     =20
> /usr/local/mysql/lib/mysql/libmysqlclient.a(libmysql.o)=20
>=20
> :=20
>=20
> ;=20
>=20
> ;
>  ; __floatdidf                         0x4094    =20
> /usr/local/mysql/lib/mysql/libmysqlclient.a(libmysql.o)=20
>=20
> __floatdisf                         0x401c    =20
> /usr/local/mysql/lib/mysql/libmysqlclient.a(libmysql.o)=20
>=20
> __muldi3                            0x78      =20
> /usr/local/mysql/lib/mysql/libmysqlclient.a(longlong2str.o)=20
>=20
> __muldi3                            0x984     =20
> /usr/local/mysql/lib/mysql/libmysqlclient.a(ctype-simple.o)=20
>=20
> __muldi3                            0xc18     =20
> /usr/local/mysql/lib/mysql/libmysqlclient.a(ctype-simple.o)=20
>=20
> __muldi3                            0x22c     =20
> /usr/local/mysql/lib/mysql/libmysqlclient.a(my_strtoll10.o)=20
>=20
> __muldi3                            0x3f8     =20
> /usr/local/mysql/lib/mysql/libmysqlclient.a(my_strtoll10.o)=20
>=20
> __muldi3                            0x440     =20
> /usr/local/mysql/lib/mysql/libmysqlclient.a(my_strtoll10.o)=20
>=20
> __udivdi3                           0x5c      =20
> /usr/local/mysql/lib/mysql/libmysqlclient.a(longlong2str.o)=20
>=20
> __udivdi3                           0x204     =20
> /usr/local/mysql/lib/mysql/libmysqlclient.a(longlong2str.o)=20
>=20
> __udivdi3                           0x8d4     =20
> /usr/local/mysql/lib/mysql/libmysqlclient.a(ctype-simple.o)=20
>=20
> __udivdi3                           0xb68     =20
> /usr/local/mysql/lib/mysql/libmysqlclient.a(ctype-simple.o)=20
>=20
> __udivdi3                           0xe74     =20
> /usr/local/mysql/lib/mysql/libmysqlclient.a(ctype-simple.o)=20
>=20
> __umoddi3                           0x8f8     =20
> /usr/local/mysql/lib/mysql/libmysqlclient.a(ctype-simple.o)=20
>=20
> __umoddi3                           0xb8c     =20
> /usr/local/mysql/lib/mysql/libmysqlclient.a(ctype-simple.o)=20
>=20
> ld: fatal: relocations remain against allocatable but non-writable sectio=
ns=20
>=20
> collect2: ld returned 1 exit status=20
>=20
>  =20
>=20
> Thx=20
>=20
>  =20
>=20
>  =20
> =20
>  ________________________________
> =20
>=20
> From: Steven Leung=20
>  Sent: Tuesday, January 04, 2005 12:54 AM
>  To: Oren Miller; qui...@li...
>  Subject: RE: [Quickfix-developers] Problem on compiling with MySQL=20
> =20
>=20
>  =20
> =20
> =20
>=20
> Oren,=20
> =20
>=20
>  =20
> =20
>=20
>     My OS is Solaris 8 and compiler is gcc 3.4.2. And the MySQL itself is
> running properly.=20
> =20
>=20
>  =20
> =20
>=20
> Thx=20
> =20
>=20
> Steven=20
> =20
>  ________________________________
> =20
> =20
>=20
> From: Oren Miller [mailto:or...@qu...]
>  Sent: Tue 1/4/2005 12:55 AM
>  To: Steven Leung; qui...@li...
>  Subject: Re: [Quickfix-developers] Problem on compiling with MySQL=20
> =20
> =20
>=20
> Steven,=20
> =20
>=20
>  =20
> =20
>=20
> Please give details on the operating system and compiler you are using.=
=20
> Thanks.=20
> =20
>=20
>  =20
> =20
>=20
> --oren=20
> =20
> =20
>=20
> ----- Original Message -----=20
> =20
>=20
> From: Steven Leung=20
> =20
>=20
> To: qui...@li...=20
> =20
>=20
> Sent: Monday, January 03, 2005 10:26 AM=20
> =20
>=20
> Subject: [Quickfix-developers] Problem on compiling with MySQL=20
> =20
>=20
>  =20
> =20
>=20
> Hi,=20
> =20
>=20
>       When I compile quickfix 1.9.4 with MySQL option, everything was fin=
e
> in './configure ' and 'make'. However when I try to 'make install', it sh=
ow
> a huge page of errors, a part of it as follows:=20
> =20
>=20
>  =20
> =20
>=20
> ............=20
> =20
> =20
>=20
> sqlclient.a(ctype-simple.o)
>  __udivdi3                           0xb68     =20
> /usr/local/mysql/lib/mysql/libmysqlclient.a(ctype-simple.o)
>  __udivdi3                           0xe74     =20
> /usr/local/mysql/lib/mysql/libmysqlclient.a(ctype-simple.o)
>  __umoddi3                           0x8f8     =20
> /usr/local/mysql/lib/mysql/libmysqlclient.a(ctype-simple.o)
>  __umoddi3                           0xb8c     =20
> /usr/local/mysql/lib/mysql/libmysqlclient.a(ctype-simple.o)
>  ld: fatal: relocations remain against allocatable but non-writable secti=
ons
> collect2: ld returned 1 exit status
>  libtool: install: error: relink `libquickfix_jni.la' with the above comm=
and
> before installing it
>  make[2]: *** [install-libLTLIBRARIES] Error 1
>  make[2]: Leaving directory `/usr/local/src/quickfix/src/java'
>  make[1]: *** [install-am] Error 2
>  make[1]: Leaving directory `/usr/local/src/quickfix/src/java'
>  make: *** [install-recursive] Error 1=20
> =20
>=20
>  =20
> =20
>=20
> Please advice.=20
> =20
>=20
>  =20
> =20
>=20
> Thanks a lot!=20
> =20
>=20
> Steven=20


--=20
Caleb Epstein
caleb dot epstein at gmail dot com