|
From: Minh K. <min...@gm...> - 2020-05-07 06:49:08
|
Something I found, when I loop and get the specific session SessionID lvSessionID = lvIterator.next(); > After that I set the value for this SessionID (SenderCompID and TargetCompID field): mvSettings.setString(lvSessionID, SenderCompID, Value); > This time I try to retrieve the value from SessionID again: lvSessionID.getTargetCompID() ===> The value is empty now (not updated yet) So why it cannot update after I use this apit mvSettings.setString(lvSessionID, SenderCompID, Value); ? Vào Th 5, 7 thg 5, 2020 vào lúc 13:11 Minh Kha <min...@gm...> đã viết: > More information, even I see the SessionSetting have value for > SenderCompID and TargetCompID, but the quickfix log show that they did not > get those yet. > May 07, 2020 12:28:24 PM quickfix.DefaultSessionSchedule <init> > INFO: [FIX.4.4:->] weekly, SUN 00:00:00-UTC - SAT 23:59:59-UTC > > => INFO: [FIX.4.4:->SenderCompID->TargetCompID] should have been like that. > > Vào Th 5, 7 thg 5, 2020 vào lúc 12:40 Minh Kha <min...@gm...> > đã viết: > >> Hi Mr, >> >> I have a problem like that: the SessionSetting was initialized without >> sendercompid and targetcompid specifed at first, after that I set the value >> for those by using another config file from another place. Using the api >> setting.setString(lvSessionID, Key, Value) >> >> Before the thread of initiator was start, I can see the SessionSetting >> instance already had the value for SenderCompID and TargetCompID. However, >> after start that thread, seems it did not get the SenderCompID and >> TargetCompID value, so cause the issue of unknown session >> >> Could u pls give me some idea about this ? Very appreciated with any reply >> >> Thank you. >> >> -- >> *Phan Nguyen Minh Kha* >> min...@gm... / 0938499460 >> > > > -- > *Phan Nguyen Minh Kha* > min...@gm... / 0938499460 > -- *Phan Nguyen Minh Kha* min...@gm... / 0938499460 |