RE: [Quickfix-developers] Issues in quickfix v1.8.0

[James C. D. <jc...@co...>]

Himanshu,
Could you expand a little on the scenario described in paragraph 1 below and
possible send fragments of the incoming and outgoing logs that illustrate
this? 


Jim
 
James C. Downs
Connamara Systems, LLC
53 W. Jackson Blvd
Suite 1627
Chicago, IL 60604
312 - 282 - 7746
www.connamara.com

-----Original Message-----
From: qui...@li...
[mailto:qui...@li...] On Behalf Of Sharma
Himanshu
Sent: Monday, October 11, 2004 11:01 AM
To: qui...@li...
Subject: [Quickfix-developers] Issues in quickfix v1.8.0

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 am using QuickFIX v1.8.0 on Solaris. I am running QuickFIX as part of a
test tool where we send get lot of executions in a very short span of time.

Some of the issues I observed are:

1. If the counterparty engine send a wrong message. Ex. sends an execution
for NewOrderSingle with tag 39=2 and then follows it up with 39=1, the
quickfix library causes itself the session to be disconnected.[Event log
shows: "Disconnecting"]. The outgoing log shows that FIX library had
actually sent Logon message. No logoff message is seen.

2. All subsequent send command returns me exception but the cause of
expection is empty. [ex.what() == ""]. Detailed examination also showed
Session::sendRaw() blocks at the m_application.toAdmin() or
m_application.toApp().

3. I am also using ACE where, we have redirected std::cerr as STDERR. Now
when I try to do a std::cout from within Application::fromApp(), i never see
the output. Nor does ACE_DEBUG() works. But if I do std::cerr, it works
fine. Also when I am sending message, i can do std::cout without problem.

4. In case if the recvQueue has some messages pending, it does not allow me
to disconnect the session [using ThreadedInitiator::stop()].

I am using SynchonizedApplication class in the initiator boot. The
Application class sets itself with SynchonizedApplication class. The
Initiator used is ThreadedSocketInitiator().

Is there any sense in all this? Has anyone faced such problems before.

Also how can i know if the physical socket connection is still valid. Is
there any method which allows me to purge messages in recvQueue, before I
try disconnecting the session?

Thanks in advance, since this is a lengthy message and the situation is bit
confusing even for me!

Regards,
Himanshu

_________________________________________________________________
Movies, music, celeb news. Stay in the loop. http://www.msn.co.in/cinema/
With MSN Entertainment!



-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Quickfix-developers mailing list
Qui...@li...
https://lists.sourceforge.net/lists/listinfo/quickfix-developers