quickfix-developers — QuickFIX developers forum

Re: [Quickfix-developers] queuing of messages

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

On 4/21/06, Mike Smith <MS...@rj...> wrote:
>
>
> During the downtime for a session, where does QuickFix store the queued
> up messages it will send once the session starts up again?  I'm using
> MSSQLStore, but don't see any tables where this data would be stored.
> If it's stored in memory, what happens if the app is shutdown before the
> queued messages can be sent?


The messages should appear in the Store you're using, in this case the
"messages" table in your SQL server database.  QuickFIX doesn't cache them
in its own memory, at least not when using the MSSQLStore.  All resends wil=
l
be accomplished by reading messages back from the database and resending
those.

--
Caleb Epstein
caleb dot epstein at gmail dot com

[Quickfix-developers] queuing of messages

[Mike S. <MS...@rj...>]

Hi all,  I have a generic question regarding the queuing of messages.

During the downtime for a session, where does QuickFix store the queued
up messages it will send once the session starts up again?  I'm using
MSSQLStore, but don't see any tables where this data would be stored.
If it's stored in memory, what happens if the app is shutdown before the
queued messages can be sent?

Thanks,

Mike

Re: [Quickfix-developers] Crash w/QF 1.11.1

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

Is this the only time you have seen this?  Was anything else going on at 
the time?  Were there other connected sessions?  Was there a disconnect 
and reconnect.  Any additional information about what was happening at 
the time would be helpful.

--oren

Andrew Munn wrote:

> QuickFIX Documentation: 
> http://www.quickfixengine.org/quickfix/doc/html/index.html
> QuickFIX Support: http://www.quickfixengine.org/services.html
>
> My application, using ThreadedSocketAcceptor, just crashed when a 
> client connected.  some of the error scrolled off the screen but I was 
> left with this:
>
> in a notification box:" Runtime Error: program: 
> c:\jdk1.0.0_06\bin\java.exe  This applications has requested the 
> Runtime to terminate it in an unusual way. Please contact the 
> applicatin's support team for mroe information."
>
> in the dos cmd window:
>
>   at Session::next(.\Session.cpp:1185)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at Session::next(.\Session.cpp:1185)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at Session::next(.\Session.cpp:1185)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at Session::next(.\Session.cpp:1185)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at Session::next(.\Session.cpp:1185)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at Session::next(.\Session.cpp:1185)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at Session::next(.\Session.cpp:1185)
>   at Session::next(.\Session.cpp:1185)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at Session::next(.\Session.cpp:1185)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at Session::next(.\Session.cpp:1185)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at Session::next(.\Session.cpp:1185)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at Session::next(.\Session.cpp:1185)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at Session::next(.\Session.cpp:1185)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at Session::next(.\Session.cpp:1185)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at Session::next(.\Session.cpp:1185)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at Session::next(.\Session.cpp:1185)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at Session::next(.\Session.cpp:1185)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at Session::next(.\Session.cpp:1185)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at Session::next(.\Session.cpp:1185)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at Session::next(.\Session.cpp:1185)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at Session::next(.\Session.cpp:1185)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at Session::next(.\Session.cpp:1185)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at Session::next(.\Session.cpp:1185)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at Session::next(.\Session.cpp:1185)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at Session::next(.\Session.cpp:1185)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at Session::next(.\Session.cpp:1185)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at Session::next(.\Session.cpp:1185)
>   at Session::next(.\Session.cpp:1185)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at Session::next(.\Session.cpp:1185)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at Session::next(.\Session.cpp:1185)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at Session::next(.\Session.cpp:1211)
>   at Session::next(.\Session.cpp:1185)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at Session::next(.\Session.cpp:1185)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at Session::next(.\Session.cpp:1185)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at Session::next(.\Session.cpp:1185)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at Session::next(.\Session.cpp:1211)
>   at Session::next(.\Session.cpp:1185)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at Session::next(.\Session.cpp:1185)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at Session::next(.\Session.cpp:1185)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at Session::next(.\Session.cpp:1185)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at Session::next(.\Session.cpp:1185)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at Session::next(.\Session.cpp:1185)
>   at Session::next(.\Session.cpp:1185)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at Session::next(.\Session.cpp:1185)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at Session::next(.\Session.cpp:1185)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at Session::next(.\Session.cpp:1185)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at Session::next(.\Session.cpp:1185)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at Session::next(.\Session.cpp:1185)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at Session::next(.\Session.cpp:1185)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at 
> ThreadedSocketAcceptor::socketThread(.\ThreadedSocketAcceptor.cpp:186)
> thread(3548):
>   at process_sleep(.\Utility.cpp:372)
>   at ThreadedSocketInitiator::onStart(.\ThreadedSocketInitiator.cpp:72)
>   at Initiator::startThread(.\Initiator.cpp:240)
> thread(3596):
>   at message_order::operator=(.\MessageSorters.cpp:65)
>   at Session::nextQueued(.\Session.cpp:1157)
>   at Session::nextQueued(.\Session.cpp:1151)
>   at Session::nextHeartbeat(.\Session.cpp:255)
>   at Session::next(.\Session.cpp:1211)
>   at Session::next(.\Session.cpp:1185)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at 
> ThreadedSocketInitiator::socketThread(.\ThreadedSocketInitiator.cpp:214)
> thread(3668):struct FIX::IOException: IO Error
>   at Session::lookupSession(.\Session.cpp:1395)
>   at Session::lookupSession(.\Session.cpp:1408)
>   at 
> ThreadedSocketConnection::setSession(.\ThreadedSocketConnection.cpp:167)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at 
> ThreadedSocketAcceptor::socketThread(.\ThreadedSocketAcceptor.cpp:186)
> thread(3716):
>   at process_sleep(.\Utility.cpp:372)
>   at ThreadedSocketInitiator::onStart(.\ThreadedSocketInitiator.cpp:72)
>   at Initiator::startThread(.\Initiator.cpp:240)
> thread(3732):class std::logic_error: MsgSeqNum too low, expecting 19 
> but receive
> d 7
>   at Session::lookupSession(.\Session.cpp:1395)
>   at Session::lookupSession(.\Session.cpp:1408)
>   at 
> ThreadedSocketConnection::setSession(.\ThreadedSocketConnection.cpp:167)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at 
> ThreadedSocketAcceptor::socketThread(.\ThreadedSocketAcceptor.cpp:186)
> thread(3856):
>   at FieldMap::clear(.\FieldMap.cpp:165)
>   at FieldMap::operator=(.\FieldMap.cpp:40)
>   at Session::sendRaw(.\Session.cpp:428)
>   at Session::send(.\Session.cpp:418)
>   at Session::sendToTarget(.\Session.cpp:1348)
> thread(4020):
>   at message_order::operator=(.\MessageSorters.cpp:65)
>   at Session::nextQueued(.\Session.cpp:1157)
>   at Session::nextQueued(.\Session.cpp:1151)
>   at Session::nextHeartbeat(.\Session.cpp:255)
>   at Session::next(.\Session.cpp:1211)
>   at Session::next(.\Session.cpp:1185)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at 
> ThreadedSocketInitiator::socketThread(.\ThreadedSocketInitiator.cpp:214)
> thread(4080):
>   at message_order::operator=(.\MessageSorters.cpp:65)
>   at Session::nextQueued(.\Session.cpp:1157)
>   at Session::nextQueued(.\Session.cpp:1151)
>   at Session::nextHeartbeat(.\Session.cpp:255)
>   at Session::next(.\Session.cpp:1211)
>   at Session::next(.\Session.cpp:1185)
>   at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139) 
>
>
>   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>   at 
> ThreadedSocketInitiator::socketThread(.\ThreadedSocketInitiator.cpp:214)
> thread(2168):
>   at process_sleep(.\Utility.cpp:372)
>   at ThreadedSocketInitiator::onStart(.\ThreadedSocketInitiator.cpp:72)
>   at Initiator::startThread(.\Initiator.cpp:240)
> thread(2776):
>   at process_sleep(.\Utility.cpp:372)
>   at ThreadedSocketInitiator::onStart(.\ThreadedSocketInitiator.cpp:72)
>   at Initiator::startThread(.\Initiator.cpp:240)
> thread(3388):
>   at process_sleep(.\Utility.cpp:372)
>   at ThreadedSocketInitiator::onStart(.\ThreadedSocketInitiator.cpp:72)
>   at Initiator::startThread(.\Initiator.cpp:240)
> thread(3396):
>   at process_sleep(.\Utility.cpp:372)
>   at ThreadedSocketInitiator::onStart(.\ThreadedSocketInitiator.cpp:72)
>   at Initiator::startThread(.\Initiator.cpp:240)
> thread(3716):
>   at process_sleep(.\Utility.cpp:372)
>   at ThreadedSocketInitiator::onStart(.\ThreadedSocketInitiator.cpp:72)
>   at Initiator::startThread(.\Initiator.cpp:240)
>
> Thanks,
> Andrew
>
>
> -------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job 
> easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache 
> Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
>
>

Re: [Quickfix-developers] SocketInitiator Windows C++ bottleneck

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

On 4/21/06, George Damusis <mic...@co...> wrote:

> I single stepped into the FIX::SocketIiniator () function only to end up
> in an assembly code section deep within the bowels of the Microsoft and/o=
r
> QuickFix library code. Any time one gets in that deep looking for an
> obscure exception, the problem is probably one that can be solved right a=
way
> only by an expert quickfix developer who knows from personal experience
> that the cause is a certain library file or external dependency that is
> missing. If any one of you out there has a clue please let me know. Thank
> you=85
>
You might try building a debug version of your application and looking at
the stack when the exceptions are thrown.  Linking with a debug version of
the QuickFIX library might be helpful as well.

For someone who claims to be an experienced developer, you seem to be
expending very little effort debugging.

--
Caleb Epstein
caleb dot epstein at gmail dot com

Re: [Quickfix-developers] Crash w/QF 1.11.1

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

sorry - that should have been jdk1.5.0_06

On Fri, 21 Apr 2006, Andrew Munn wrote:

> QuickFIX Documentation: 
> http://www.quickfixengine.org/quickfix/doc/html/index.html
> QuickFIX Support: http://www.quickfixengine.org/services.html
>
> My application, using ThreadedSocketAcceptor, just crashed when a client 
> connected.  some of the error scrolled off the screen but I was left with 
> this:
>
> in a notification box:" Runtime Error: program: c:\jdk1.0.0_06\bin\java.exe 
> This applications has requested the Runtime to terminate it in an unusual 
> way. Please contact the applicatin's support team for mroe information."
>
> in the dos cmd window:
>
>  at Session::next(.\Session.cpp:1185)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at Session::next(.\Session.cpp:1185)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at Session::next(.\Session.cpp:1185)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at Session::next(.\Session.cpp:1185)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at Session::next(.\Session.cpp:1185)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at Session::next(.\Session.cpp:1185)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at Session::next(.\Session.cpp:1185)
>  at Session::next(.\Session.cpp:1185)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at Session::next(.\Session.cpp:1185)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at Session::next(.\Session.cpp:1185)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at Session::next(.\Session.cpp:1185)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at Session::next(.\Session.cpp:1185)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at Session::next(.\Session.cpp:1185)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at Session::next(.\Session.cpp:1185)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at Session::next(.\Session.cpp:1185)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at Session::next(.\Session.cpp:1185)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at Session::next(.\Session.cpp:1185)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at Session::next(.\Session.cpp:1185)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at Session::next(.\Session.cpp:1185)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at Session::next(.\Session.cpp:1185)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at Session::next(.\Session.cpp:1185)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at Session::next(.\Session.cpp:1185)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at Session::next(.\Session.cpp:1185)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at Session::next(.\Session.cpp:1185)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at Session::next(.\Session.cpp:1185)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at Session::next(.\Session.cpp:1185)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at Session::next(.\Session.cpp:1185)
>  at Session::next(.\Session.cpp:1185)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at Session::next(.\Session.cpp:1185)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at Session::next(.\Session.cpp:1185)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at Session::next(.\Session.cpp:1211)
>  at Session::next(.\Session.cpp:1185)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at Session::next(.\Session.cpp:1185)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at Session::next(.\Session.cpp:1185)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at Session::next(.\Session.cpp:1185)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at Session::next(.\Session.cpp:1211)
>  at Session::next(.\Session.cpp:1185)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at Session::next(.\Session.cpp:1185)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at Session::next(.\Session.cpp:1185)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at Session::next(.\Session.cpp:1185)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at Session::next(.\Session.cpp:1185)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at Session::next(.\Session.cpp:1185)
>  at Session::next(.\Session.cpp:1185)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at Session::next(.\Session.cpp:1185)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at Session::next(.\Session.cpp:1185)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at Session::next(.\Session.cpp:1185)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at Session::next(.\Session.cpp:1185)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at Session::next(.\Session.cpp:1185)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at Session::next(.\Session.cpp:1185)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at ThreadedSocketAcceptor::socketThread(.\ThreadedSocketAcceptor.cpp:186)
> thread(3548):
>  at process_sleep(.\Utility.cpp:372)
>  at ThreadedSocketInitiator::onStart(.\ThreadedSocketInitiator.cpp:72)
>  at Initiator::startThread(.\Initiator.cpp:240)
> thread(3596):
>  at message_order::operator=(.\MessageSorters.cpp:65)
>  at Session::nextQueued(.\Session.cpp:1157)
>  at Session::nextQueued(.\Session.cpp:1151)
>  at Session::nextHeartbeat(.\Session.cpp:255)
>  at Session::next(.\Session.cpp:1211)
>  at Session::next(.\Session.cpp:1185)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at ThreadedSocketInitiator::socketThread(.\ThreadedSocketInitiator.cpp:214)
> thread(3668):struct FIX::IOException: IO Error
>  at Session::lookupSession(.\Session.cpp:1395)
>  at Session::lookupSession(.\Session.cpp:1408)
>  at ThreadedSocketConnection::setSession(.\ThreadedSocketConnection.cpp:167)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at ThreadedSocketAcceptor::socketThread(.\ThreadedSocketAcceptor.cpp:186)
> thread(3716):
>  at process_sleep(.\Utility.cpp:372)
>  at ThreadedSocketInitiator::onStart(.\ThreadedSocketInitiator.cpp:72)
>  at Initiator::startThread(.\Initiator.cpp:240)
> thread(3732):class std::logic_error: MsgSeqNum too low, expecting 19 but 
> receive
> d 7
>  at Session::lookupSession(.\Session.cpp:1395)
>  at Session::lookupSession(.\Session.cpp:1408)
>  at ThreadedSocketConnection::setSession(.\ThreadedSocketConnection.cpp:167)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at ThreadedSocketAcceptor::socketThread(.\ThreadedSocketAcceptor.cpp:186)
> thread(3856):
>  at FieldMap::clear(.\FieldMap.cpp:165)
>  at FieldMap::operator=(.\FieldMap.cpp:40)
>  at Session::sendRaw(.\Session.cpp:428)
>  at Session::send(.\Session.cpp:418)
>  at Session::sendToTarget(.\Session.cpp:1348)
> thread(4020):
>  at message_order::operator=(.\MessageSorters.cpp:65)
>  at Session::nextQueued(.\Session.cpp:1157)
>  at Session::nextQueued(.\Session.cpp:1151)
>  at Session::nextHeartbeat(.\Session.cpp:255)
>  at Session::next(.\Session.cpp:1211)
>  at Session::next(.\Session.cpp:1185)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at ThreadedSocketInitiator::socketThread(.\ThreadedSocketInitiator.cpp:214)
> thread(4080):
>  at message_order::operator=(.\MessageSorters.cpp:65)
>  at Session::nextQueued(.\Session.cpp:1157)
>  at Session::nextQueued(.\Session.cpp:1151)
>  at Session::nextHeartbeat(.\Session.cpp:255)
>  at Session::next(.\Session.cpp:1211)
>  at Session::next(.\Session.cpp:1185)
>  at 
> ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)
>
>  at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
>  at ThreadedSocketInitiator::socketThread(.\ThreadedSocketInitiator.cpp:214)
> thread(2168):
>  at process_sleep(.\Utility.cpp:372)
>  at ThreadedSocketInitiator::onStart(.\ThreadedSocketInitiator.cpp:72)
>  at Initiator::startThread(.\Initiator.cpp:240)
> thread(2776):
>  at process_sleep(.\Utility.cpp:372)
>  at ThreadedSocketInitiator::onStart(.\ThreadedSocketInitiator.cpp:72)
>  at Initiator::startThread(.\Initiator.cpp:240)
> thread(3388):
>  at process_sleep(.\Utility.cpp:372)
>  at ThreadedSocketInitiator::onStart(.\ThreadedSocketInitiator.cpp:72)
>  at Initiator::startThread(.\Initiator.cpp:240)
> thread(3396):
>  at process_sleep(.\Utility.cpp:372)
>  at ThreadedSocketInitiator::onStart(.\ThreadedSocketInitiator.cpp:72)
>  at Initiator::startThread(.\Initiator.cpp:240)
> thread(3716):
>  at process_sleep(.\Utility.cpp:372)
>  at ThreadedSocketInitiator::onStart(.\ThreadedSocketInitiator.cpp:72)
>  at Initiator::startThread(.\Initiator.cpp:240)
>
> Thanks,
> Andrew
>
>
> -------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
>

[Quickfix-developers] Crash w/QF 1.11.1

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

My application, using ThreadedSocketAcceptor, just crashed when a client 
connected.  some of the error scrolled off the screen but I was left with 
this:

in a notification box:" Runtime Error: program: 
c:\jdk1.0.0_06\bin\java.exe  This applications has requested the Runtime to terminate it in an 
unusual way. Please contact the applicatin's support team for mroe 
information."

in the dos cmd window:

   at Session::next(.\Session.cpp:1185)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at Session::next(.\Session.cpp:1185)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at Session::next(.\Session.cpp:1185)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at Session::next(.\Session.cpp:1185)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at Session::next(.\Session.cpp:1185)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at Session::next(.\Session.cpp:1185)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at Session::next(.\Session.cpp:1185)
   at Session::next(.\Session.cpp:1185)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at Session::next(.\Session.cpp:1185)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at Session::next(.\Session.cpp:1185)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at Session::next(.\Session.cpp:1185)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at Session::next(.\Session.cpp:1185)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at Session::next(.\Session.cpp:1185)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at Session::next(.\Session.cpp:1185)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at Session::next(.\Session.cpp:1185)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at Session::next(.\Session.cpp:1185)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at Session::next(.\Session.cpp:1185)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at Session::next(.\Session.cpp:1185)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at Session::next(.\Session.cpp:1185)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at Session::next(.\Session.cpp:1185)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at Session::next(.\Session.cpp:1185)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at Session::next(.\Session.cpp:1185)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at Session::next(.\Session.cpp:1185)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at Session::next(.\Session.cpp:1185)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at Session::next(.\Session.cpp:1185)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at Session::next(.\Session.cpp:1185)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at Session::next(.\Session.cpp:1185)
   at Session::next(.\Session.cpp:1185)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at Session::next(.\Session.cpp:1185)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at Session::next(.\Session.cpp:1185)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at Session::next(.\Session.cpp:1211)
   at Session::next(.\Session.cpp:1185)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at Session::next(.\Session.cpp:1185)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at Session::next(.\Session.cpp:1185)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at Session::next(.\Session.cpp:1185)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at Session::next(.\Session.cpp:1211)
   at Session::next(.\Session.cpp:1185)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at Session::next(.\Session.cpp:1185)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at Session::next(.\Session.cpp:1185)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at Session::next(.\Session.cpp:1185)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at Session::next(.\Session.cpp:1185)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at Session::next(.\Session.cpp:1185)
   at Session::next(.\Session.cpp:1185)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at Session::next(.\Session.cpp:1185)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at Session::next(.\Session.cpp:1185)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at Session::next(.\Session.cpp:1185)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at Session::next(.\Session.cpp:1185)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at Session::next(.\Session.cpp:1185)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at Session::next(.\Session.cpp:1185)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at 
ThreadedSocketAcceptor::socketThread(.\ThreadedSocketAcceptor.cpp:186)
thread(3548):
   at process_sleep(.\Utility.cpp:372)
   at ThreadedSocketInitiator::onStart(.\ThreadedSocketInitiator.cpp:72)
   at Initiator::startThread(.\Initiator.cpp:240)
thread(3596):
   at message_order::operator=(.\MessageSorters.cpp:65)
   at Session::nextQueued(.\Session.cpp:1157)
   at Session::nextQueued(.\Session.cpp:1151)
   at Session::nextHeartbeat(.\Session.cpp:255)
   at Session::next(.\Session.cpp:1211)
   at Session::next(.\Session.cpp:1185)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at 
ThreadedSocketInitiator::socketThread(.\ThreadedSocketInitiator.cpp:214)
thread(3668):struct FIX::IOException: IO Error
   at Session::lookupSession(.\Session.cpp:1395)
   at Session::lookupSession(.\Session.cpp:1408)
   at 
ThreadedSocketConnection::setSession(.\ThreadedSocketConnection.cpp:167)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at 
ThreadedSocketAcceptor::socketThread(.\ThreadedSocketAcceptor.cpp:186)
thread(3716):
   at process_sleep(.\Utility.cpp:372)
   at ThreadedSocketInitiator::onStart(.\ThreadedSocketInitiator.cpp:72)
   at Initiator::startThread(.\Initiator.cpp:240)
thread(3732):class std::logic_error: MsgSeqNum too low, expecting 19 but 
receive
d 7
   at Session::lookupSession(.\Session.cpp:1395)
   at Session::lookupSession(.\Session.cpp:1408)
   at 
ThreadedSocketConnection::setSession(.\ThreadedSocketConnection.cpp:167)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at 
ThreadedSocketAcceptor::socketThread(.\ThreadedSocketAcceptor.cpp:186)
thread(3856):
   at FieldMap::clear(.\FieldMap.cpp:165)
   at FieldMap::operator=(.\FieldMap.cpp:40)
   at Session::sendRaw(.\Session.cpp:428)
   at Session::send(.\Session.cpp:418)
   at Session::sendToTarget(.\Session.cpp:1348)
thread(4020):
   at message_order::operator=(.\MessageSorters.cpp:65)
   at Session::nextQueued(.\Session.cpp:1157)
   at Session::nextQueued(.\Session.cpp:1151)
   at Session::nextHeartbeat(.\Session.cpp:255)
   at Session::next(.\Session.cpp:1211)
   at Session::next(.\Session.cpp:1185)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at 
ThreadedSocketInitiator::socketThread(.\ThreadedSocketInitiator.cpp:214)
thread(4080):
   at message_order::operator=(.\MessageSorters.cpp:65)
   at Session::nextQueued(.\Session.cpp:1157)
   at Session::nextQueued(.\Session.cpp:1151)
   at Session::nextHeartbeat(.\Session.cpp:255)
   at Session::next(.\Session.cpp:1211)
   at Session::next(.\Session.cpp:1185)
   at 
ThreadedSocketConnection::processStream(.\ThreadedSocketConnection.cpp:139)

   at ThreadedSocketConnection::read(.\ThreadedSocketConnection.cpp:76)
   at 
ThreadedSocketInitiator::socketThread(.\ThreadedSocketInitiator.cpp:214)
thread(2168):
   at process_sleep(.\Utility.cpp:372)
   at ThreadedSocketInitiator::onStart(.\ThreadedSocketInitiator.cpp:72)
   at Initiator::startThread(.\Initiator.cpp:240)
thread(2776):
   at process_sleep(.\Utility.cpp:372)
   at ThreadedSocketInitiator::onStart(.\ThreadedSocketInitiator.cpp:72)
   at Initiator::startThread(.\Initiator.cpp:240)
thread(3388):
   at process_sleep(.\Utility.cpp:372)
   at ThreadedSocketInitiator::onStart(.\ThreadedSocketInitiator.cpp:72)
   at Initiator::startThread(.\Initiator.cpp:240)
thread(3396):
   at process_sleep(.\Utility.cpp:372)
   at ThreadedSocketInitiator::onStart(.\ThreadedSocketInitiator.cpp:72)
   at Initiator::startThread(.\Initiator.cpp:240)
thread(3716):
   at process_sleep(.\Utility.cpp:372)
   at ThreadedSocketInitiator::onStart(.\ThreadedSocketInitiator.cpp:72)
   at Initiator::startThread(.\Initiator.cpp:240)

Thanks,
Andrew

[Quickfix-developers] SocketInitiator Windows C++ bottleneck

[George D. <mic...@co...>]

I can=92t get past the very first socket initiator failure. I=92m
programming with Microsoft Studio=92s Visual C++ in the Windows
environment to produce a Windows program that is equivalent to the
example program supplied by quickfixengine=92s tradeclient program for
initiating a buy side session. I tried the example versions of
tradeclient and executor in two MS Windows command windows and saw that
they communicated properly with heartbeat transmissions and responses to
the tradeclient order selections on my local computer. I=92m trying to =
do
the same with my Windows client program, but I can=92t get past the
FIX::SocketInitiator initiator( theApp, storeFactory, settings );
command that is followed by the initiator.start(); command. In debug
mode, after one single step past the SocketInitiator command I get the
following four exception messages in my Visual C++ compiler=92s output
window:
First-chance exception in FixBuy.exe (KERNEL32.DLL): 0xE06D7363:
Microsoft C++ Exception.
First-chance exception in FixBuy.exe (KERNEL32.DLL): 0xE06D7363:
Microsoft C++ Exception.
First-chance exception in FixBuy.exe (KERNEL32.DLL): 0xE06D7363:
Microsoft C++ Exception.
First-chance exception in FixBuy.exe (KERNEL32.DLL): 0xE06D7363:
Microsoft C++ Exception.
=20
Upon return from this routine I get the message:
First-chance exception in FixBuy.exe: 0xC0000005: Access Violation.
=20
I single stepped into the FIX::SocketIiniator () function only to end up
in an assembly code section deep within the bowels of the Microsoft
and/or QuickFix library code. Any time one gets in that deep looking for
an obscure exception, the problem is probably one that can be solved
right away only by an expert quickfix developer who knows from personal
experience that the cause is a certain library file or external
dependency that is missing. If any one of you out there has a clue
please let me know. Thank you=85    =20
=20
=20

--=20
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.385 / Virus Database: 268.4.4/320 - Release Date: 4/20/2006
=20

RE: [Quickfix-developers] trying to test FIX communication Windows C++ code locally

[George D. <mic...@co...>]

Caleb,
Thank you for your reply. Let me now state, that the most important
prerequisite for me with every new programming task undertaken, was to
fully understand the program flow and mechanics of the new task at hand.
If I didn=92t understand that part, I simply couldn=92t put a program
together in a reasonable amount of time, even if I was an expert in the
programming language I was using to do it. I can eventually produce a
program, but only at great cost to me and my employer in terms of trial
and error hours. What I was hoping to avoid here was the excessive
initial hours. I did try the sample programs individually and
scrutinized their source code. However, I didn=92t connect the dots to =
try
the Trade Client program and the Executor program together. It never
occurred to me that these two programs were designed to handshake
locally, not remotely, as this was never explicitly mentioned in the
examples web page. Loading them both with their command line
configuration files as command line arguments was also not even
mentioned. Without the configuration files, the programs would exit as
soon as they came up. I finally adapted all this new found knowledge and
the two programs worked locally in two separate Windows command windows,
and exhibited the program flow and mechanics of operation that I was
looking for. Had two simple sentences explicitly stating how to use the
example programs been supplied on the web site, it would have saved me
many hours of head scratching. So thanks for calling my attention to the
example programs, as it gave me the idea to try them out concurrently.
If I gain any kind of expertise with this FIX programming, I=92ll write =
up
a concise and useful Getting Started type of programmer guide for the
QuickfixEngine website that will eliminate a lot of the guesswork, that
I would bet every new FIX programmer goes through when trying to
implement a FIX communications program for the first time.
=20
In the meantime I still would appreciate a look at anyone else=92s
Microsoft Windows C++ FIX API code, if that programmer is agreeable to
offering that most precious gift of source code to a stranger. I plan to
do the same once I get my source code developed.
Thanks,
George Damusis  =20
=20
-----Original Message-----
From: qui...@li...
[mailto:qui...@li...] On Behalf Of
Caleb Epstein
Sent: Thursday, April 20, 2006 2:42 PM
To: George Damusis
Cc: qui...@li...
Subject: Re: [Quickfix-developers] trying to test FIX communication
Windows C++ code locally
=20
=20
On 4/20/06, George Damusis <HYPERLINK
"mailto:mic...@co..."mic...@co...> wrote:
After supplying a valid sample configuration file for defining the
SessionSettings, and then running the  FIX::SocketInitiator initiator(
theApp, storeFactory, settings ); and  initiator.start(); commands, all
I get is an Exception error from the SocketInitiator.cpp module. This is
obviously due to the lack of a proper connection to a counterparty
acceptor site. I'd love to know how my code can be tested in tight
functional segments on my local computer?
What exception is being thrown?  You have likely forgotten to specify
some required configuration parameter.  You can catch the exception and
print out the result of its what() method for a potentially useful error
message.=20
Any advice from any quickfix developer with experience would surely be
appreciated. In fact I would be very grateful to communicate with a
quickfix developer who has created an initiator side quickfix program
specifically for use in a Microsoft Windows C++ environment.
There are several example programs included that should work out of the
box.  Have you tried using them as a jumping-off point?  See
specifically examples/tradeclient and  HYPERLINK
"file:///C:\\DOCUME~1\\nbde52d\\LOCALS~1\\Temp\\moz-screenshot.jpg"examp
les/executor/C++.

--=20
Caleb Epstein
caleb dot epstein at gmail dot com=20
--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.385 / Virus Database: 268.4.4/319 - Release Date: 4/19/2006

--=20
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.385 / Virus Database: 268.4.4/319 - Release Date: 4/19/2006
=20

Re: [Quickfix-developers] trying to test FIX communication Windows C++ code locally

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

On 4/20/06, George Damusis <mic...@co...> wrote:
>
>  After supplying a valid sample configuration file for defining the
> SessionSettings, and then running the  FIX::SocketInitiator initiator(
> theApp, storeFactory, settings ); and  initiator.start(); commands, all I
> get is an Exception error from the SocketInitiator.cpp module. This is
> obviously due to the lack of a proper connection to a counterparty accept=
or
> site. I'd love to know how my code can be tested in tight functional
> segments on my local computer?
>
What exception is being thrown?  You have likely forgotten to specify some
required configuration parameter.  You can catch the exception and print ou=
t
the result of its what() method for a potentially useful error message.

> Any advice from any quickfix developer with experience would surely be
> appreciated. In fact I would be very grateful to communicate with a
> quickfix developer who has created an initiator side quickfix program
> specifically for use in a Microsoft Windows C++ environment.
>
There are several example programs included that should work out of the
box.  Have you tried using them as a jumping-off point?  See specifically
examples/tradeclient and examples/executor/C++.

--
Caleb Epstein
caleb dot epstein at gmail dot com

[Quickfix-developers] trying to test FIX communication Windows C++ code locally

[George D. <mic...@co...>]

I=92m an old Visual C++ 6.0 developer with lots of real time market data
handling experience, but I=92m new to FIX protocol. I=92ve looked at all =
the
sample code and examples in the documentation section of the
quickfixengine site, and while it has been helpful, it has not connected
enough of the dots to for this newbie to figure out how to test the most
basic session creation and logon messages. After supplying a valid
sample configuration file for defining the SessionSettings, and then
running the  FIX::SocketInitiator initiator( theApp, storeFactory,
settings ); and  initiator.start(); commands, all I get is an Exception
error from the SocketInitiator.cpp module. This is obviously due to the
lack of a proper connection to a counterparty acceptor site. I=92d love =
to
know how my code can be tested in tight functional segments on my local
computer?=20
=20
Any advice from any quickfix developer with experience would surely be
appreciated. In fact I would be very grateful to communicate with a
quickfix developer who has created an initiator side quickfix program
specifically for use in a Microsoft Windows C++ environment.
Thanks,
George Damusis
Mic...@co...=20

--=20
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.385 / Virus Database: 268.4.4/319 - Release Date: 4/19/2006
=20

[Quickfix-developers] Access violation

[Fad <s.f...@gm...>]

When my application try to create a Socket Acceptor with the following code,
I have this error: Access violation at address 00007972. Read of address
00007972

std::string file = cfgfile;
FIX::SessionSettings settings(file);
KCApplication *application = new KCApplication;

application->appdata=appdata;
FIX::FileStoreFactory storeFactory( settings );
FIX::FileLogFactory logFactory( settings );

application->acceptor = new FIX::SocketAcceptor( *application,
storeFactory,settings,logFactory );

This is my configuration ini file

[DEFAULT]
ConnectionType=acceptor
SocketAcceptPort=5005
HeartBtInt=30
FileStorePath=c:\sphera\quickfix\S_FIX_MKT\store
FileLogPath=c:\sphera\quickfix\S_FIX_MKT\log
StartTime=00:00:00
EndTime=23:59:59
StartDay= Monday
EndDay= Sunday
TimeZone=Europe/Rome
DoNotPersistTypes=X:W
DoNotLogTypes=X:W

[SESSION]
BeginString=FIX.4.2
SenderCompID=SNSRVFIXMKT
TargetCompID=FINECOFIXMKT
DataDictionary=c:\sphera\lib\FIX42.xml

N.B.
If each time, before execute my application, I delete the log and store file
I don't have the error.

Someone can help me..?
--
View this message in context: http://www.nabble.com/Access-violation-t1479335.html#a4003797
Sent from the QuickFIX - Dev forum at Nabble.com.

Re: [Quickfix-developers] [OFF TOPIC] How did you make and test the project files for visual studio?

[Dale W. <wil...@oc...>]

Hi Clark,

This is off topic, but it might be of general interest.

You should take a look at MPC (Make Project Creator) -- an open source=20
project developed and supported by my company, OCI.

    http://www.ociweb.com/products/mpc

Using the same very simple project definition files can generate=20
projects for VC6, VC7, VC8, and make files for gcc, sunCC, and a host of=20
other build tool sets.
.
For example in recent project I defined a workspace (aka solution)=20
containing two projects like so:

workspace {
   TSL
   TSL_UT
}

In the TSL directory

project: {
  sharedname =3D TSL
  dynamicflags +=3D TSL_BUILD_DLL
}

generates a DLL named TSL.dll using every cpp & .h file in the TSL=20
directory,

while in the TSL_UT directory

project {
  exename =3D TSL_UT
  libs +=3D TSL
  lit_libs +=3D libboost_unit_test_framework-vc71-mt-gd-1_33_1
  after +=3D TSL
}

which uses all the source files in TSL_UT to generate an EXE.  The=20
TSL.lib and and  the boost unit test framework are linked in, and there=20
is a build order dependency on TSL.

This is a fairly simple example, but MPC is also used in much more=20
complicated situations.  It is used to generate all of the make files=20
and project files for ACE and TAO -- a cross platform library that runs=20
on dozens of platforms and involves thousands of source files -- many of=20
them generated by compilers, parser generators, etc.

and, of course, MPC free for the downloading.

Dale



Clark Sims wrote:
> I have been doing a conslting gig for about 6 months. I have had a=20
> horrilbe time getting projects to port from one windows box to another.
>
> When I create a project directory, compile everytthing, zip it and=20
> ship it, it never seems to work on the other side.
>
> Likewise when another developer sends me a ziped project directory=20
> try, I have to open up the project, replace all of the relative path=20
> names with absolute names, and recompile everything from scratch.
>
> I would have sworn quickfix used nmake to compile the Microsoft code,=20
> but when I went to the website today, I saw project files!  How in the=20
> world did you make all of these project files?  Did you point and=20
> click and add all of the files by hand? That seems like a Herculean tas=
k!
>
> How did you get the project files to port across different machines? =20
> I can't do this for anything!
>
> -----------------------------------------------------------------------=
-
> Love cheap thrills? Enjoy PC-to-Phone calls to 30+ countries=20
> <http://us.rd.yahoo.com/mail_us/taglines/postman9/*http://us.rd.yahoo.c=
om/evt=3D39666/*http://beta.messenger.yahoo.com/>=20
> for just 2=A2/min with Yahoo! Messenger with Voice.=20

[Quickfix-developers] Mutex into "getter" and "setter" of SessionState class

[<que...@bn...>]

Hi All,

The way the mutex is used into methodes from SessionState, do not allows to
desynchronize completly incoming and outgoing treatments.
ie: if you are are calling getNextTargetMsgSeqNum(), that get the next seq
num from the cache, you could have to wait for the end of
incrNextSenderMsgSeqNum(), that store seq num into DB.

Therefore optimization, with used of mutex, can be done into class SessionState.

What do you think ?

Thanks & rgds,

Quentin.



This message and any attachments (the "message") is
intended solely for the addressees and is confidential. 
If you receive this message in error, please delete it and 
immediately notify the sender. Any use not in accord with 
its purpose, any dissemination or disclosure, either whole 
or partial, is prohibited except formal approval. The internet
can not guarantee the integrity of this message. 
BNP PARIBAS (and its subsidiaries) shall (will) not 
therefore be liable for the message if modified. 

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

Ce message et toutes les pieces jointes (ci-apres le 
"message") sont etablis a l'intention exclusive de ses 
destinataires et sont confidentiels. Si vous recevez ce 
message par erreur, merci de le detruire et d'en avertir 
immediatement l'expediteur. Toute utilisation de ce 
message non conforme a sa destination, toute diffusion 
ou toute publication, totale ou partielle, est interdite, sauf 
autorisation expresse. L'internet ne permettant pas 
d'assurer l'integrite de ce message, BNP PARIBAS (et ses
filiales) decline(nt) toute responsabilite au titre de ce 
message, dans l'hypothese ou il aurait ete modifie.

Re: [Quickfix-developers] java server help

[Joerg T. <Joe...@ma...>]

Hi Ralph,

> Using the older version of quickfix (notquickfixj). Coding in java.=20
> Having problem getting the executor to resping to a login by a fix=20
> client. I see the sessions start up (again using the executor example)=20
> but the client connects, send a logon, then immediately disconnects.

Typical cause maybe a clock difference between the two machines. If QF de=
tects a clock=20
difference larger than the MaxLatency settting, its disconnects. Try to s=
et CheckLatency=3DN=20
to find out whether this is the reason.

Other reason is connecting with a sequence number too low. Please send de=
tailed logs,=20
preferably from both sides, if the above hints do not help.

> Question is, do I need to implement this functionality? When the=20
> acceptor starts a session is the session level part of the fix protocol=
=20
> handled "out of the box" with quickfix or do I need to implement it.=20

QF implements the full session level protocol out of the box for you. You=
 can use the=20
callbacks (to/from Admin/App) to influence specific aspects.

Cheers, J=F6rg

--=20
Joerg Thoennes
                                http://macd.com
Tel.: +49 (0)241 44597-24      Macdonald Associates GmbH
Fax : +49 (0)241 44597-10      Lothringer Str. 52, D-52070 Aachen

[Quickfix-developers] How did you make and test the project files for visual studio?

[Clark S. <cla...@ya...>]

I have been doing a conslting gig for about 6 months. I have had a horrilbe time getting projects to port from one windows box to another.

When I create a project directory, compile everytthing, zip it and ship it, it never seems to work on the other side.

Likewise when another developer sends me a ziped project directory try, I have to open up the project, replace all of the relative path names with absolute names, and recompile everything from scratch.

I would have sworn quickfix used nmake to compile the Microsoft code, but when I went to the website today, I saw project files!  How in the world did you make all of these project files?  Did you point and click and add all of the files by hand? That seems like a Herculean task!

How did you get the project files to port across different machines?  I can't do this for anything!

		
---------------------------------
Love cheap thrills? Enjoy PC-to-Phone  calls to 30+ countries for just 2¢/min with Yahoo! Messenger with Voice.

[Quickfix-developers] java server help

[Ralph D. <ra...@ra...>]

Using the older version of quickfix (notquickfixj). Coding in java. Having 
problem getting the executor to resping to a login by a fix client. I see 
the sessions start up (again using the executor example) but the client 
connects, send a logon, then immediately disconnects. Question is, do I 
need to implement this functionality? When the acceptor starts a session is 
the session level part of the fix protocol handled "out of the box" with 
quickfix or do I need to implement it. Sorry, first time using quickfix. 
Thanks so much for any help.

Re: [Quickfix-developers] strange error when moving app to new server

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

Heh, should have read your second message before responding to the =20
first.  That's good because I didn't find anything :).

--oren

On Apr 18, 2006, at 9:31 AM, Mike Smith wrote:

> QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/=20
> html/index.html
> QuickFIX Support: http://www.quickfixengine.org/services.html
>
> I just found the problem, I guess all it takes is sending out an =20
> email,
> then you instantly get smarter.  I tried running the runat debug on =20=

> the
> 2003 server and it complained about not having ntwdblib.dll.  After I
> put that file on the server, everything worked.
>
> -mike
>
> -----Original Message-----
> From: qui...@li...
> [mailto:qui...@li...] On Behalf Of
> Mike Smith
> Sent: Tuesday, April 18, 2006 8:30 AM
> To: qui...@li...
> Subject: [Quickfix-developers] strange error when moving app to new
> server
>
> QuickFIX Documentation:
> http://www.quickfixengine.org/quickfix/doc/html/index.html
> QuickFIX Support: http://www.quickfixengine.org/services.html
>
> Hi all,
>
> I'm having a very troubling issue trying to install a QuickFIX
> application on a windows 2003 server.
>
> I've got a windows .net (2.0) service that I've created, which uses
> QuickFIX.  I've developed and tested it on my machine, and it runs =20
> like
> a champ.  I'm now having an issue when I try to deploy it to a
> production windows 2003 server.
>
> When I run installUtil, I get a vague error saying that it was =20
> unable to
> get the installer types.  I've been unable to get past this error.
>
> On the 2003 server I have installed the .NET 2.0 Framework, =20
> the .NET 2.0
> SDK and MSXML3.  I did not want to install the full Visual Studio 2005
> as this is a production server.  I also have installed the
> quickfix_net.dll and quickfix_net_messages.dll in the GAC (and have
> tried with it not in the GAC).
>
> What I've done, is create a brand new windows service application and
> successfully installed it on the server.  I then have added one .cs =20=

> file
> at a time (from my quickfix application) to see which file would cause
> it to error.  I then found the guilty file, which is the first one to
> actually use QuickFIX.  The actual class is in the bottom of this =20
> email.
> I have no idea what to do at this point.  I figure that since I =20
> have the
> same quickfix_net.dll and quickfix_net_messages.dll that I'm using =20
> on my
> machine, which work great, that the QuickFix stuff should have all it
> needs.  I've also tried running it as a console application and get a
> very strange 'file not found' error right away when I run it, even
> though I can't see it hitting any code which would look for a file.
>
> I'm basically stuck right now as I've been trying to get this to work
> for 2 days straight.  The code works great on my machine and is =20
> ready to
> move to production, I just need to get past this.  If anyone has ANY
> ideas, please send them on, I'm willing to try anything at this point.
>
> Thanks,
>
> Mike
>
>
>
>
>
>
> using System;
> using System.Collections.Generic;
> using System.Text;
>
> using QuickFix;
>
> namespace FIX
> {
>     public class CorrelationClOrdID : QuickFix.StringField
>     {
>         public CorrelationClOrdID() : base(9717) { }
>         public CorrelationClOrdID(String data) : base(9717, data) { }
>     }
>
>     public class CtiCode : QuickFix.CharField
>     {
>         public CtiCode() : base(9702) { }
>         public CtiCode(Char data) : base(9702, data) { }
>     }
>
>     public class OriginatorUserId : QuickFix.StringField
>     {
>         public OriginatorUserId() : base(9139) { }
>         public OriginatorUserId(String data) : base(9139, data) { }
>     }
>
>     public class ProductId : QuickFix.IntField
>     {
>         public ProductId() : base(9061) { }
>         public ProductId(int data) : base(9061, data) { }
>     }
>
>     public class SequenceId : QuickFix.IntField
>     {
>         public SequenceId() : base(9141) { }
>         public SequenceId(int data) : base(9141, data) { }
>     }
>
>     public class OrderState : QuickFix.IntField
>     {
>         public OrderState() : base(9175) { }
>         public OrderState(int data) : base(9175, data) { }
>     }
>
>     public class BlockVolume : QuickFix.DoubleField
>     {
>         public BlockVolume() : base(9103) { }
>         public BlockVolume(double data) : base(9103, data) { }
>     }
>
>     public class EfpVolume : QuickFix.DoubleField
>     {
>         public EfpVolume() : base(9106) { }
>         public EfpVolume(double data) : base(9106, data) { }
>     }
>
>     public class EfsVolume : QuickFix.DoubleField
>     {
>         public EfsVolume() : base(9107) { }
>         public EfsVolume(double data) : base(9107, data) { }
>     }
>
>     public class CustomerAccountRefId : QuickFix.StringField
>     {
>         public CustomerAccountRefId() : base(9207) { }
>         public CustomerAccountRefId(String data) : base(9207, data) =20=

> { }
>     }
> }
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting
> language
> that extends applications into web and mobile media. Attend the live
> webcast
> and join the prime developer group breaking into this new coding
> territory!
> http://sel.as-us.falkag.net/sel?cmd=3Dk&kid=110944&bid$1720&dat=121642
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting =20
> language
> that extends applications into web and mobile media. Attend the =20
> live webcast
> and join the prime developer group breaking into this new coding =20
> territory!
> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=110944&bid$1720&dat=121642=

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

Re: [Quickfix-developers] strange error when moving app to new server

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

Mike,

I think that one of the release build in the vs8 solution may be =20
using a debug DLL.  Let me verify this is the case.

--oren

On Apr 18, 2006, at 8:29 AM, Mike Smith wrote:

> QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/=20
> html/index.html
> QuickFIX Support: http://www.quickfixengine.org/services.html
>
> Hi all,
>
> I'm having a very troubling issue trying to install a QuickFIX
> application on a windows 2003 server.
>
> I've got a windows .net (2.0) service that I've created, which uses
> QuickFIX.  I've developed and tested it on my machine, and it runs =20
> like
> a champ.  I'm now having an issue when I try to deploy it to a
> production windows 2003 server.
>
> When I run installUtil, I get a vague error saying that it was =20
> unable to
> get the installer types.  I've been unable to get past this error.
>
> On the 2003 server I have installed the .NET 2.0 Framework, =20
> the .NET 2.0
> SDK and MSXML3.  I did not want to install the full Visual Studio 2005
> as this is a production server.  I also have installed the
> quickfix_net.dll and quickfix_net_messages.dll in the GAC (and have
> tried with it not in the GAC).
>
> What I've done, is create a brand new windows service application and
> successfully installed it on the server.  I then have added one .cs =20=

> file
> at a time (from my quickfix application) to see which file would cause
> it to error.  I then found the guilty file, which is the first one to
> actually use QuickFIX.  The actual class is in the bottom of this =20
> email.
> I have no idea what to do at this point.  I figure that since I =20
> have the
> same quickfix_net.dll and quickfix_net_messages.dll that I'm using =20
> on my
> machine, which work great, that the QuickFix stuff should have all it
> needs.  I've also tried running it as a console application and get a
> very strange 'file not found' error right away when I run it, even
> though I can't see it hitting any code which would look for a file.
>
> I'm basically stuck right now as I've been trying to get this to work
> for 2 days straight.  The code works great on my machine and is =20
> ready to
> move to production, I just need to get past this.  If anyone has ANY
> ideas, please send them on, I'm willing to try anything at this point.
>
> Thanks,
>
> Mike
>
>
>
>
>
>
> using System;
> using System.Collections.Generic;
> using System.Text;
>
> using QuickFix;
>
> namespace FIX
> {
>     public class CorrelationClOrdID : QuickFix.StringField
>     {
>         public CorrelationClOrdID() : base(9717) { }
>         public CorrelationClOrdID(String data) : base(9717, data) { }
>     }
>
>     public class CtiCode : QuickFix.CharField
>     {
>         public CtiCode() : base(9702) { }
>         public CtiCode(Char data) : base(9702, data) { }
>     }
>
>     public class OriginatorUserId : QuickFix.StringField
>     {
>         public OriginatorUserId() : base(9139) { }
>         public OriginatorUserId(String data) : base(9139, data) { }
>     }
>
>     public class ProductId : QuickFix.IntField
>     {
>         public ProductId() : base(9061) { }
>         public ProductId(int data) : base(9061, data) { }
>     }
>
>     public class SequenceId : QuickFix.IntField
>     {
>         public SequenceId() : base(9141) { }
>         public SequenceId(int data) : base(9141, data) { }
>     }
>
>     public class OrderState : QuickFix.IntField
>     {
>         public OrderState() : base(9175) { }
>         public OrderState(int data) : base(9175, data) { }
>     }
>
>     public class BlockVolume : QuickFix.DoubleField
>     {
>         public BlockVolume() : base(9103) { }
>         public BlockVolume(double data) : base(9103, data) { }
>     }
>
>     public class EfpVolume : QuickFix.DoubleField
>     {
>         public EfpVolume() : base(9106) { }
>         public EfpVolume(double data) : base(9106, data) { }
>     }
>
>     public class EfsVolume : QuickFix.DoubleField
>     {
>         public EfsVolume() : base(9107) { }
>         public EfsVolume(double data) : base(9107, data) { }
>     }
>
>     public class CustomerAccountRefId : QuickFix.StringField
>     {
>         public CustomerAccountRefId() : base(9207) { }
>         public CustomerAccountRefId(String data) : base(9207, data) =20=

> { }
>     }
> }
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting =20
> language
> that extends applications into web and mobile media. Attend the =20
> live webcast
> and join the prime developer group breaking into this new coding =20
> territory!
> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=110944&bid$1720&dat=121642=

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

RE: [Quickfix-developers] strange error when moving app to new server

[Mike S. <MS...@rj...>]

I just found the problem, I guess all it takes is sending out an email,
then you instantly get smarter.  I tried running the runat debug on the
2003 server and it complained about not having ntwdblib.dll.  After I
put that file on the server, everything worked.

-mike

-----Original Message-----
From: qui...@li...
[mailto:qui...@li...] On Behalf Of
Mike Smith
Sent: Tuesday, April 18, 2006 8:30 AM
To: qui...@li...
Subject: [Quickfix-developers] strange error when moving app to new
server

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

Hi all,

I'm having a very troubling issue trying to install a QuickFIX
application on a windows 2003 server.

I've got a windows .net (2.0) service that I've created, which uses
QuickFIX.  I've developed and tested it on my machine, and it runs like
a champ.  I'm now having an issue when I try to deploy it to a
production windows 2003 server. =20

When I run installUtil, I get a vague error saying that it was unable to
get the installer types.  I've been unable to get past this error.

On the 2003 server I have installed the .NET 2.0 Framework, the .NET 2.0
SDK and MSXML3.  I did not want to install the full Visual Studio 2005
as this is a production server.  I also have installed the
quickfix_net.dll and quickfix_net_messages.dll in the GAC (and have
tried with it not in the GAC).

What I've done, is create a brand new windows service application and
successfully installed it on the server.  I then have added one .cs file
at a time (from my quickfix application) to see which file would cause
it to error.  I then found the guilty file, which is the first one to
actually use QuickFIX.  The actual class is in the bottom of this email.
I have no idea what to do at this point.  I figure that since I have the
same quickfix_net.dll and quickfix_net_messages.dll that I'm using on my
machine, which work great, that the QuickFix stuff should have all it
needs.  I've also tried running it as a console application and get a
very strange 'file not found' error right away when I run it, even
though I can't see it hitting any code which would look for a file.

I'm basically stuck right now as I've been trying to get this to work
for 2 days straight.  The code works great on my machine and is ready to
move to production, I just need to get past this.  If anyone has ANY
ideas, please send them on, I'm willing to try anything at this point.

Thanks,

Mike






using System;
using System.Collections.Generic;
using System.Text;

using QuickFix;

namespace FIX
{
    public class CorrelationClOrdID : QuickFix.StringField
    {
        public CorrelationClOrdID() : base(9717) { }
        public CorrelationClOrdID(String data) : base(9717, data) { }
    }

    public class CtiCode : QuickFix.CharField
    {
        public CtiCode() : base(9702) { }
        public CtiCode(Char data) : base(9702, data) { }
    }

    public class OriginatorUserId : QuickFix.StringField
    {
        public OriginatorUserId() : base(9139) { }
        public OriginatorUserId(String data) : base(9139, data) { }
    }

    public class ProductId : QuickFix.IntField
    {
        public ProductId() : base(9061) { }
        public ProductId(int data) : base(9061, data) { }
    }

    public class SequenceId : QuickFix.IntField
    {
        public SequenceId() : base(9141) { }
        public SequenceId(int data) : base(9141, data) { }
    }
   =20
    public class OrderState : QuickFix.IntField
    {
        public OrderState() : base(9175) { }
        public OrderState(int data) : base(9175, data) { }
    }

    public class BlockVolume : QuickFix.DoubleField
    {
        public BlockVolume() : base(9103) { }
        public BlockVolume(double data) : base(9103, data) { }
    }

    public class EfpVolume : QuickFix.DoubleField
    {=20
        public EfpVolume() : base(9106) { }
        public EfpVolume(double data) : base(9106, data) { }
    }

    public class EfsVolume : QuickFix.DoubleField
    {
        public EfsVolume() : base(9107) { }
        public EfsVolume(double data) : base(9107, data) { }
    }

    public class CustomerAccountRefId : QuickFix.StringField
    {
        public CustomerAccountRefId() : base(9207) { }
        public CustomerAccountRefId(String data) : base(9207, data) { }
    }
}


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting
language
that extends applications into web and mobile media. Attend the live
webcast
and join the prime developer group breaking into this new coding
territory!
http://sel.as-us.falkag.net/sel?cmd=3Dk&kid=110944&bid$1720&dat=121642
_______________________________________________
Quickfix-developers mailing list
Qui...@li...
https://lists.sourceforge.net/lists/listinfo/quickfix-developers

[Quickfix-developers] strange error when moving app to new server

[Mike S. <MS...@rj...>]

Hi all,

I'm having a very troubling issue trying to install a QuickFIX
application on a windows 2003 server.

I've got a windows .net (2.0) service that I've created, which uses
QuickFIX.  I've developed and tested it on my machine, and it runs like
a champ.  I'm now having an issue when I try to deploy it to a
production windows 2003 server. =20

When I run installUtil, I get a vague error saying that it was unable to
get the installer types.  I've been unable to get past this error.

On the 2003 server I have installed the .NET 2.0 Framework, the .NET 2.0
SDK and MSXML3.  I did not want to install the full Visual Studio 2005
as this is a production server.  I also have installed the
quickfix_net.dll and quickfix_net_messages.dll in the GAC (and have
tried with it not in the GAC).

What I've done, is create a brand new windows service application and
successfully installed it on the server.  I then have added one .cs file
at a time (from my quickfix application) to see which file would cause
it to error.  I then found the guilty file, which is the first one to
actually use QuickFIX.  The actual class is in the bottom of this email.
I have no idea what to do at this point.  I figure that since I have the
same quickfix_net.dll and quickfix_net_messages.dll that I'm using on my
machine, which work great, that the QuickFix stuff should have all it
needs.  I've also tried running it as a console application and get a
very strange 'file not found' error right away when I run it, even
though I can't see it hitting any code which would look for a file.

I'm basically stuck right now as I've been trying to get this to work
for 2 days straight.  The code works great on my machine and is ready to
move to production, I just need to get past this.  If anyone has ANY
ideas, please send them on, I'm willing to try anything at this point.

Thanks,

Mike






using System;
using System.Collections.Generic;
using System.Text;

using QuickFix;

namespace FIX
{
    public class CorrelationClOrdID : QuickFix.StringField
    {
        public CorrelationClOrdID() : base(9717) { }
        public CorrelationClOrdID(String data) : base(9717, data) { }
    }

    public class CtiCode : QuickFix.CharField
    {
        public CtiCode() : base(9702) { }
        public CtiCode(Char data) : base(9702, data) { }
    }

    public class OriginatorUserId : QuickFix.StringField
    {
        public OriginatorUserId() : base(9139) { }
        public OriginatorUserId(String data) : base(9139, data) { }
    }

    public class ProductId : QuickFix.IntField
    {
        public ProductId() : base(9061) { }
        public ProductId(int data) : base(9061, data) { }
    }

    public class SequenceId : QuickFix.IntField
    {
        public SequenceId() : base(9141) { }
        public SequenceId(int data) : base(9141, data) { }
    }
   =20
    public class OrderState : QuickFix.IntField
    {
        public OrderState() : base(9175) { }
        public OrderState(int data) : base(9175, data) { }
    }

    public class BlockVolume : QuickFix.DoubleField
    {
        public BlockVolume() : base(9103) { }
        public BlockVolume(double data) : base(9103, data) { }
    }

    public class EfpVolume : QuickFix.DoubleField
    {=20
        public EfpVolume() : base(9106) { }
        public EfpVolume(double data) : base(9106, data) { }
    }

    public class EfsVolume : QuickFix.DoubleField
    {
        public EfsVolume() : base(9107) { }
        public EfsVolume(double data) : base(9107, data) { }
    }

    public class CustomerAccountRefId : QuickFix.StringField
    {
        public CustomerAccountRefId() : base(9207) { }
        public CustomerAccountRefId(String data) : base(9207, data) { }
    }
}

Re: [Quickfix-developers] Create Socket Acceptor

[Fad <s.f...@gm...>]

Resolved, in the configuring ini file I had not written the StartDay and
EndDay.
--
View this message in context: http://www.nabble.com/Create-Socket-Acceptor-t1443069.html#a3965080
Sent from the QuickFIX - Dev forum at Nabble.com.

[Quickfix-developers] JNI ClassLoader changes

[Anshu N. <ans...@ya...>]

Hi ,

We are upgrading from 1.9.4 to 1.11.1 does this build
have the below mentioned fix for JNI ClassLoader
changes .


http://www.quickfixengine.org/bugtracker/bug.php?op=show&bugid=58&pos=0



If it doesn't then from where do I get the above
mentioned patch for 1.11.1 or can I apply that as is .

Thanks and Regrads,
Anshu Narang.


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

[Quickfix-developers] Create Socket Acceptor

[Fad <s.f...@gm...>]

If in the session's file store there are something like this:
20060412-06:52:38
and the current day is different, for example today: 13

when my application try to create a Socket Acceptor with this code:

std::string file = cfgfile;
FIX::SessionSettings settings(file);
KCApplication *application = new KCApplication;

application->appdata=appdata;
FIX::FileStoreFactory storeFactory( settings );
FIX::FileLogFactory logFactory( settings );

application->acceptor = new FIX::SocketAcceptor( *application,
storeFactory,settings,logFactory );

the system try an Exception.. if I manually change the date in session's
file store with current day.. the system work correctly. Why?

Stafano
	
--
View this message in context: http://www.nabble.com/Create-Socket-Acceptor-t1443069.html#a3896911
Sent from the QuickFIX - Dev forum at Nabble.com.

[Quickfix-developers] Sequence Reset

[Anshu N. <ans...@ya...>]

Hi ,

I Just wanted to ensure that sequence number should be
reset  before quickfix engine ( 1.9.4 ) send a logon
message.

I have set these two properties in cfg file 

ResetOnLogout=Y
ResetOnDisconnect=Y

also I do a Session.lookupSession(sessionID).reset();
in onCreate method . 

Do I need to do anything else to ensure this . 

Regards,
Anshu Narang.

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

RE: [Quickfix-developers] source for 15 minute delayed quotes

[Steve B. <sb...@sm...>]

Hi Clark,
=20
I don't have any sources of 15 minute delayed feeds but
http://www.opentick.com/ has free historical data and has real-time
feeds available for only the exchange fees (ECN data has no exchange
fees). You could delay it yourself, if needed. If there any possibility
you will open source your simulator?
=20
Steve=20


________________________________

	From: qui...@li...
[mailto:qui...@li...] On Behalf Of
Clark Sims
	Sent: Wednesday, April 12, 2006 7:21 PM
	To: QuickFIX
	Subject: [Quickfix-developers] source for 15 minute delayed
quotes
=09
=09
	I would like to build an order matching engine, for simulating
real time trading with fix clients in the development stages.
=09
	I would like to make this engine available to anyone who
registers a testing account with me. This will be a free service.
=09
	I have tried the order matching / testing engines at SLK, Arca,
and two other firms. All of them fall short.
=09
	I would like to have bids and offers which reflect the market
conditions delayed by 15 minutes, so that all information is considered
public information, and I don't have to worry about disseminating
prices.
=09
	What is a good source of 15 minute delayed data?
=09

=09
________________________________

	New Yahoo! Messenger with Voice. Call regular phones from your
PC
<http://us.rd.yahoo.com/mail_us/taglines/postman5/*http://us.rd.yahoo.co
m/evt=3D39666/*http://beta.messenger.yahoo.com>  and save big.