史蒂夫!非常感谢您的回答。最后在我的逻辑类中,我创建了一个单例来处理 Hazelcast 实例——比如
final static String DistributedMapName = "SystemUserActivityMap";
private static HazelcastInstance instance = Hazelcast.newHazelcastInstance();
我还创建了一个hazelcast.xml,非常简单
<network>
<port auto-increment="true">5701</port>
<join>
<multicast enabled="false">
<multicast-group>224.2.2.3</multicast-group>
<multicast-port>54327</multicast-port>
</multicast>
<tcp-ip enabled="true">
<interface>127.0.0.1</interface>
</tcp-ip>
<aws enabled="false">
</aws>
</join>
</network>
<map name="SystemUserActivityMap">...
起初一切似乎都很好,但后来我在 tomcat 错误日志消息中注意到 hazelcast 不时启动新端口,所以在启动后不久
Members [1] {
Member [127.0.0.1]:5701 this
}
现在它
Members [9] {
Member [127.0.0.1]:5701
Member [127.0.0.1]:5702
Member [127.0.0.1]:5703
Member [127.0.0.1]:5704
Member [127.0.0.1]:5705
Member [127.0.0.1]:5706
Member [127.0.0.1]:5707 this
Member [127.0.0.1]:5708
Member [127.0.0.1]:5709
}
并继续增长......我不明白为什么它在这台机器上使用所有这些端口