Hi,
Your assumptions are correct. There is also an issue [1] that likely is
causing this behavior. As a workaround you can try to force IgniteContext to
start everything in client mode. In order to achieve this, use
setClientMode(true) in the closure that created IgniteConfiguration:
IgniteOutClosure ioc = new IgniteOutClosure() {
@Override
public Object apply() {
IgniteConfiguration cfg = new IgniteConfiguration();
cfg.setClientMode(true);
cfg.setCacheConfiguration(cacheCfg);
return cfg;
}
};
[1] https://issues.apache.org/jira/browse/IGNITE-5981
-Val
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
