SocketInitiator getSession 给出会话的顺序与配置文件中的顺序不同

SocketInitiator getSession give session not at the same order as in the config file

当我尝试通过包含 sessionConfig 的文件中存在的索引获取 sessionconfig 时(在我们的例子中 "InitiatorSettings.cfg")

[default]
FileStorePath=data
FileLogPath=log
HeartBtInt=30
ReconnectInterval=5

[session] 
SessionName=badisInit1
BeginString=FIX.4.2
SenderCompID=client1
TargetCompID=server1
ConnectionType=initiator
SocketConnectPort=9878
SocketConnectHost=localhost
UseDataDictionary=N

[session] 
SessionName=init0badis
BeginString=FIX.4.2
SenderCompID=client1
TargetCompID=server12
ConnectionType=initiator
SocketConnectPort=9878
SocketConnectHost=localhost
UseDataDictionary=N

[session] 
SessionName=test211
BeginString=FIX.4.2
SenderCompID=badis
TargetCompID=server
ConnectionType=initiator
SocketConnectPort=9878
SocketConnectHost=localhost
UseDataDictionary=N

我以不同的顺序获得会话,仅在前两个会话 ID 中:

 get session id FIX.4.2:client1->server12
 get session id FIX.4.2:client1->server1
 get session id FIX.4.2:badis->server

有我用来加载会话并打印它们的代码 不知道是文件中和我们加载后顺序不同是正常的,还是我的配置文件有问题..

        SessionSettings sessionSettings = new SessionSettings("InitiatorSettings.cfg");

        ApplicationImp mainApplication = new ApplicationImp();

        FileStoreFactory fileStoreFactory = new FileStoreFactory(sessionSettings);

        FileLogFactory logFactory = new FileLogFactory(sessionSettings);

        MessageFactory messageFactory = new DefaultMessageFactory();

        socketInitiator = new SocketInitiator( mainApplication,
                fileStoreFactory, this.sessionSettings, logFactory,
                messageFactory);

        for(int i=0;i<socketInitiator.getSessions().size();i++)
        {
            System.out.println("get session id "+socketInitiator.getSessions().get(i));
        }

感谢您的帮助。

SessionID->Sessions 存储在 HashMap 中并在 getSessions() 方法上转换为 List 时会话不排序是正常行为。

来自 SessionConnector(SocketInitiator 的超类)

public ArrayList<SessionID> getSessions() {
    return new ArrayList<SessionID>(sessions.keySet());
}

(提醒一下,HashMap 不保证 put() 调用的顺序。为此您需要 LinkedHashMap。)

除了修改核心代码之外,还有一个建议是添加一个 属性 一个有序的 sessionID 列表并遍历 属性 并在 getSessionMap()