[QFJ-630] If the quote and trade server is different then developers have no way to distinguish the session id when the configuration details for the two server are same except the host and port Created: 30/Aug/11  Updated: 13/Feb/14  Resolved: 13/Feb/14

Status: Closed
Project: QuickFIX/J
Component/s: Engine
Affects Version/s: 1.5.1
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Mansoor Haider Assignee: Laurent Danesi
Resolution: Not a bug Votes: 0
Labels: QuickfixJ, session
Environment:

windows



 Description   

If the quote and trade server is different then the session id generated for two servers are same when the configuration details for the 2 server (quote and trade server) are same except host name and port.......In this case user of the api have no idea how to distinguish between the 2 servers...

We might need to change the createID() method of of sessionID class which will generate 2 different sessionIDs..



 Comments   
Comment by Jörg Thönnes [ 02/Sep/11 ]

Hi Mansoor,

did you check the SessionQualifier:

http://www.quickfixj.org/quickfixj/usermanual/1.5.1/usage/configuration.html

This is provided for initiator only.

Cheers, Jörg

Comment by Mansoor Haider [ 02/Sep/11 ]

Hi,

First of all the use of SessionQualifier is not recommended.
Will it ensure difference in sessionID generated??
How will I identify between different sessions??
Currently we are generating random numbers and appending it to sessionID created.Are you sure a SessionQualifier does this job??

Sorry never used SessionQualifier.Therefore does not have much knowledge regarding it.It is mentioned in documentation that it makes compatibilty with jni.We donot want it to be os dependent.

Thanks

Comment by Mansoor Haider [ 02/Sep/11 ]

Hi,

I checked the sessionID class method createID() SessionQualifier gets appended to it.I dont think that it should affect the functionality of session.

Thanks

Comment by Laurent Danesi [ 19/Oct/11 ]

SessionQualifier must be used in such a case

Generated at Tue May 07 00:57:04 UTC 2024 using JIRA 7.5.2#75007-sha1:9f5725bb824792b3230a5d8716f0c13e296a3cae.