[QFJ-131] more than one connection Created: 04/Feb/07  Updated: 11/Feb/07  Resolved: 10/Feb/07

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

Type: Other Priority: Major
Reporter: Raul Alzola Assignee: Steve Bate
Resolution: Fixed Votes: 0
Labels: None
Environment:

Tomcat 5.0.28, j2ee 1.4, Windows 2003 Server



 Description   

I have a J2EE web application composed with servlets, jsp's and other components. Within the application must be posible to have two different fix connections avialable, both connecting the same IP but on different ports. Currently I have two different classes implementing Application and extending MessageCracker classes respectly. Although I start their Initialtor objects with their corresponding SettingsConfig, it seems that just the last one is avialable and all the messages sent using Session.sendToTarget(...), are sent by the last connector initated. Is there any way to use different connectors running within the same appliation?



 Comments   
Comment by Steve Bate [ 04/Feb/07 ]

Yes. Multiple connections are supported. Do your sessions have different identifiers (FIX version,target/sender compID, and session qualifier (if any))?

Comment by Raul Alzola [ 04/Feb/07 ]

Both connections have the same BeginString, SenderCompID,TargetCompID. They differs on TargetSubID and SocketConnectPort.

Comment by Steve Bate [ 10/Feb/07 ]

Current, QuickFIX and QuickFIX/J only identify sessions by FIX version and compIDs (acceptors can also use a "qualifier"). I have plans to add the ability to distinguish sessions by subID and locationID as well.

Comment by Raul Alzola [ 11/Feb/07 ]

I got to mantain 2 sessions adding the sessionQualifier field to the .properties configuration file, with a different value for any connector. That's work very well.

Thanks for your help.

Generated at Sat Nov 23 11:12:51 UTC 2024 using JIRA 7.5.2#75007-sha1:9f5725bb824792b3230a5d8716f0c13e296a3cae.