Re: [Quickfix-users] SessionQualifier and MySQL
Brought to you by:
orenmnero
From: Oren M. <or...@qu...> - 2006-03-22 09:22:13
|
Yeah, it was mostly designed to be used with initiators to get around =20= a design flaw of some systems where they have different sessions =20 using the same session identifier on different ports. The =20 functionality was not put in to enable this design flaw. I would =20 reccommend instead that you vary the compIDs as is intended by the =20 protocol. --oren On Mar 22, 2006, at 2:57 AM, Joerg Thoennes wrote: > QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/=20 > html/index.html > QuickFIX Support: http://www.quickfixengine.org/services.html > > Privet, Nikolay, > >> We're developing acceptor application, but the specific is that we =20= >> want to >> provide many clients to initiate sessions simultaneously. We use =20 >> QuickFIX >> 1.11 with MySQL storing end logging. I tried to use =20 >> SessionQualifier, but it >> doesn't works in way I expected. Two initators with same BeginString, >> SenderCompID, TargetCompID and different SessionQualifier can't logon >> simultaneously. >> On acceptor side there are no record with nonempty =20 >> SessionQualifier field in >> session table. One initator logins successfully, but all other =20 >> initator logs is flooded >> with: >> 20060321-16:41:08 : Connecting to localhost on port 5001 >> 20060321-16:41:09 : Connection succeeded >> 20060321-16:41:09 : Initiated logon request >> 20060321-16:41:09 : Socket Error: Connection reset by peer. >> 20060321-16:41:09 : Disconnecting >> Have you an idea, where is my mistake? > > The SessionQualifier was introduced -- if I recollect correctly -- =20 > to allow QF to manage several sessions with same SenderCompID and =20 > TargetCompID, _but_ different accept ports. > > Before that a QF session was uniquely identified by (BeginString, =20 > SenderCompID, TargetCompID). > > The important point in your case is that the SessionQualifier is =20 > _not_ transmitted over the wire, ie if both of your initiator =20 > clients has a different SessionQualifier configured, but connect to =20= > the _same_ port with identical (BeginString, SenderCompID, =20 > TargetCompID), QF will forward these requests to the _same_ =20 > session, which results in the disconnects (since the session is =20 > already logged on). > > Please try with different ports for each different qualifier. > > 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 > > > ------------------------------------------------------- > 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-users mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfix-users > |