[QFJ-775] FileStore: exception thrown when more than one : is used in SessionID Created: 15/Feb/14  Updated: 02/Apr/15  Resolved: 06/May/14

Status: Closed
Project: QuickFIX/J
Component/s: Engine
Affects Version/s: 1.5.3
Fix Version/s: 1.6.0

Type: Bug Priority: Default
Reporter: Kosta Panousis Assignee: Christoph John
Resolution: Fixed Votes: 0
Labels: QuickfixJ, session
Environment:

Windows



 Description   

When only the SenderSubId or TargetSubId contain a : the engine starts fine. However, when both SendSubId and TargetSubId contain colons : an exception is thrown and teh engine does not start.

For example:
SenderSubID=ABC:ABC
TargetSubID=TEST

OR

SenderSubID=ABC
TargetSubID=TEST:TEST

start fine but the following fails with (The filename, directory name, or volume label syntax is incorrect):

SenderSubID=ABC:ABC
TargetSubID=TEST:TEST

It looks like a windows problem with the : in the file names but I was hoping that something could be done to the engine to replace the : internally or another work around. Unfortunately, exchanges like the CBOE require colons in both those fields.



 Comments   
Comment by Christoph John [ 17/Feb/14 ]

I guess there is no workaround. But it should be pretty simple to mask illegal characters when creating the file store.

Comment by Kosta Panousis [ 18/Feb/14 ]

It also looks as if this problem was fixed a few years ago. Maybe only the existence of a single : was fixed? In any case, this is preventing me from using QuickFIX with CBOE. If anyone knows a work around please let me know otherwise I have switch engines.

Comment by Christoph John [ 18/Feb/14 ]

Could you please post the issue number where this has been fixed?

Comment by Christoph John [ 19/Feb/14 ]

BTW, it should work if you remove the SenderSubID and TargetSubID from your session configuration and set them programatically on outgoing messages, i.e. in the callbacks toApp() and toAdmin() of your application.

Comment by Christoph John [ 06/May/14 ]

http://sourceforge.net/p/quickfixj/code/1186/

Generated at Sat May 04 14:27:52 UTC 2024 using JIRA 7.5.2#75007-sha1:9f5725bb824792b3230a5d8716f0c13e296a3cae.