Re: [Quickfix-users] Session.m_sessionID is wrong somehow?

[Hei C. <str...@ya...>]

Nevermind.
I had the same senderID, targetID, and beginString in 2 setting properties files (1 file for each connection).
I didn't know that the underneath implementation used senderID, targetID, beginString and qualifier as the key.
Sorry.




________________________________
From: Hei Chan <str...@ya...>
To: qui...@li...
Sent: Friday, July 24, 2009 1:14:10 AM
Subject: [Quickfix-users] Session.m_sessionID is wrong somehow?

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


Hi,

I am trying to maintain 2 FIX connections at the same time to 2 different ports.

One of my classes inherits FIX::Application, and my FIX::Application::onLogon(const FIX::SessionID& sessionID) looks like:
myClass::onLogon(const FIX::SessionID& sessionID)
{
    FIX::Session* s = FIX::Session::lookupSession(*pSessionID);
    printf("onLogon sessionID=%p, session=%p, session.m_sessionID=%p\n", pSessionID, s, &s->getSessionID());
}

When the first connection is established, the log looks okay:
onLogon sessionID=0x9acef94, session=0x9acef90, session.m_sessionID=0x9acef94

However, when the second connection is established, the log looks very odd:
onLogon sessionID=0x9c1744c, session=0x9acef90, session.m_sessionID=0x9acef94

For some unknown reasons, the second session's sessionID is the first session's sessionID.

Any input is welcome.

Thanks in advance.


Cheers,
Hei